Analysis Stage

PROJECT ANALYSIS

STUDY OF THE SYSTEM

The complete system can be divided into three halves on basis of access levels.

        

A)   Administrator

B)   Manager 

Administrator:

               An administrator is the main controller of the application.  When compared to other types of users an administrator has an additional privilege to create new users manage applications and provide notifications. An administrator creates a new task, evey newly created task is placed in a specific group and is marked with status as open. Using the manage user Assignment the administrator will create of team of an individual person will be allotted with the task to be carried out.

Using the My preferences settings the creator will automatically get notified when ever the created task is changes. It also involves the display settings such as what kind if task list should be displayed whenever the user logs in and the no of tasks that should be shown when the user views the initial page. The preferences settings also includes the sorting of the available tasks based on various parameters, such as task types to display and their respective order. An administrator can also create new category of task lists, into which the future tasks can be placed.

The user management sections involve creating new users and managing existing users in terms of privilege given to them and changing passwords.

 Application configuration involves placing the task list category with a status values. The different statuses are open, closed, in progress, intermediate etc.

Notification section includes the mechanism to notify the user with the proper message related to the tasks.

 User:

            A User is a restricted member of the application where in the user has the privileges to create new tasks manage the tasks and change the status of the application or placement of the application from one category to other category, it doesn’t posses the option of creating new users and management of applications.  

 ACCESS CONTROL FOR DATA WHICH REQUIRE USER AUTHENTICATION

                    The following commands specify access control identifiers and they are typically used to authorize and authenticate the user (command codes are

shown in parentheses)

               USER NAME (USER)

·         The user identification is that which is required by the server for access to its file system. This command will normally be the first command transmitted by the user after the control connections are made (some servers may require this).

              PASSWORD (PASS)

·         This command must be immediately preceded by the user name command, and, for some sites, completes the user's identification for access control. Since password information is quite sensitive, it is desirable in general to "mask" it or suppress type out.

FEASIBILITY REPORT:

Technical Feasibility:

                      The total number of databases that were identified to build the system is 13. The major parts of the databases are categorized as administrative components and user based components. The administrative components are useful is managing the actual master date that may be necessary to maintain the consistency of the system. These databases purely used for the internal organizational needs and necessities. The user components are designed to handle to transactional states that arise upon the system where the client makes the visit for the information required to him. The user components are scheduled accept parametrical information from the uses as per the system necessity.

GUI’s:

        In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a browses interface. The GUI’S at the top level have been categorized as

·         Administration users interface

·         Employer users interface

                              The Administration users interface concentrate on the consistent in that is practically part of organizational activities and which needs proper authentication for date collation. These interfaces to the visitors with all the transactional states lute date in date deletion and date updation only with the data search capabilities. The employer user interface helps the respective actors in transactions the actual information as per their necessities with specific to the required services. The GUI’s restrict the ordinary users from mismanipulating the systems data, which can make the existing system non operational. The information with specific to their personal standards and strategies can be changed through proper privileges.

Financial Feasibility:

               If the administrator or manager has to know about the scheduled tasks, then in manual system a concentrated search has to be done, which is a time consuming process. With the designed database all these overheads are eliminated, making the actual system faster in scheduling the tasks.

              In the manual system, a large amount of finances are required to maintain the employees and their jobs. The software used in this project eliminate the investments on the employees. The system over installed and configured makes the overall system to interact with required data exchange and helps the organization in controlling costs there by increasing its profits.

MODULES:

The modules that are identified in this project are

·         Administration module

·         Task management module

·         Task scheduling module 

Administration module:

This module maintains the information about information regarding the administrator, employees who are working for the organization.  It maintains the communication with the task management module and task scheduling module.

Task management module:

This module generally maintains the information about all the tasks that are organised at the level of organization standards. Any task under the system is registered with this module.

Task scheduling module:

This module maintains information regarding the tasks that are scheduled upon the employees,. It records the date and time when a particular task will be scheduled and by what time the task will be completed.

SOFTWARE REQUIREMENT SPECIFICATION

REQUIREMENT SPECIFICATION:

          The software, Techno Task Management is designed for management of the tasks with in a management environment of an organization.

INTRODUCTION

Purpose: The main purpose for preparing this document is to give a general insight into the analysis and requirements of the existing system or situation and for determining the operating characteristics of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC)

As it describes the complete requirement of the system. It is meant for use by the developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.

Developers Responsibilities Overview:

The developer is responsible for:

                   

1) Developing the system, which meets the SRS and solving all the requirements of the system?

2) Demonstrating the system and installing the system at client's location after the acceptance testing is successful.

3) Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.

4) Conducting any user training that might be needed for using the system.

5) Maintaining the system for a period of one year after installation.         

Functional Requirements:

                                               OUTPUT DESIGN

                        Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provides a permanent copy of the results for later consultation. The various types of outputs in general are:

• External Outputs, whose destination is outside the organization.
• Internal Outputs whose destination is with in organization and they are the 
• User’s main interface with the computer.
• Operational outputs whose use is purely with in the computer department.
• Interface outputs, which involve the user in communicating directly with 

                                               Output Definition  

                     The outputs should be defined in terms of the following points:

                        . Type of the output

                        . Content of the output

                        . Format of the output

                        . Location of the output

                        . Frequency of the output

                        . Volume of the output

                        . Sequence of the output

                        It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of the output is the most suitable.

            For Example

                     . Will decimal points need to be inserted

                         . Should leading zeros be suppressed.

Output Media:

    

            In the next stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are:

            . The suitability for the device to the particular application.

            . The need for a hard copy.

            . The response time required.

            . The location of the users

            . The software and hardware available.

. The cost.

                        Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are:   

The outputs were needed to be generated as a hot copy and as well as queries to be viewed on the screen.  Keeping in view these outputs, the format for the output is taken from the outputs, which are currently beeing obtained after manual processing.  The standard printer is to be used as output media for hard copies.

INPUT DESIGN

Input design is a part of overall system design.  The main objective during the input design is as given below:

·         To produce a cost-effective method of input.

·         To archive the highest possible level of accuracy.

·         To ensure that the input is acceptable and understood by the user.

INPUT STAGES:

   

   The main input stages can be listed as below:

·         Data recording

·         Data transcription

·         Data conversion

·         Data verification

·         Data control

·         Data transmission

·         Data validation

·         Data correction

INPUT TYPES:

        It is necessary to determine the various types of inputs.  Inputs can be categorized as follows:

·         External inputs, which are prime inputs for the system.

·         Internal inputs, which are user communications with the system.

·         Operational, which are computer department’s communications to the system?

·         Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:

  

      At this stage choice has to be made about the input media.  To conclude about the input media consideration has to be given to;

   

·         Type of input

·         Flexibility of format

·         Speed

·         Accuracy

·         Verification methods

·         Rejection rates

·         Ease of correction

·         Storage and handling requirements

·         Security

·         Easy to use

·         Portabilility

            Keeping in view the above description of the input types and input media, it can be said that most of the inputs are of the form of internal and interactive.  As

Input data is to be the directly keyed in by the user, the keyboard can be considered to be the most suitable input device.

ERROR AVOIDANCE

            At this stage care is to be taken to ensure that input data remains accurate form the stage at which it is recorded up to the stage in which the data is accepted by the system.  This can be achieved only by means of careful control each time the data is handled.

ERROR DETECTION

            Even though every effort is make to avoid the occurrence of errors, still a small proportion of errors is always likely to occur, these types of errors can be discovered by using validations to check the input data.

DATA VALIDATION

            Procedures are designed to detect errors in data at a lower level of detail.  Data validations have been included in the system in almost every area where there is a possibility for the user to commit errors.  The system will not accept invalid data.  Whenever an invalid data is keyed in, the system immediately prompts the user and the user has to again key in the data and the system will accept the data only if the data is correct.  Validations have been included where necessary.

            The system is designed to be a user friendly one.  In other words the system has been designed to communicate effectively with the user.  The system has been designed with pop up menus.

USERINTERGFACE DESIGN

            It is essential to consult the system users and discuss their needs while designing the user interface:

USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:

1.    User initiated interface the user is in charge, controlling the progress of the user/computer dialogue.  In the computer-initiated interface, the computer selects the next stage in the interaction.

2.    Computer initiated interfaces

In the computer initiated interfaces the computer guides the progress of the user/computer dialogue.  Information is displayed and the user response of the computer takes action or displays further information.

USER_INITIATED INTERGFACES

User initiated interfaces fall into tow approximate classes:

1.    Command driven interfaces: In this type of interface the user inputs commands or queries which are interpreted by the computer.

2.    Forms oriented interface: The user calls up an image of the form to his/her screen and fills in the form.  The forms oriented interface is chosen because it is the best choice.

COMPUTER-INITIATED INTERFACES

The following computer – initiated interfaces were used:

1.    The menu system for the user is presented with a list of alternatives and the user chooses one; of alternatives.

2.    Questions – answer type dialog system where the computer asks question and takes action based on the basis of the users reply.

Right from the start the system is going to be menu driven, the opening menu displays the available options.  Choosing one option gives another popup menu with more options.  In this way every option leads the users to data entry form where the user can key in the data.

ERROR MESSAGE DESIGN:

            The design of error messages is an important part of the user interface design.  As user is bound to commit some errors or other while designing a system the system should be designed to be helpful by providing the user with information regarding the error he/she has committed.

           This application must be able to produce output at different modules for different inputs.

Performance Requirements:

 Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment.  It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system.  This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements.  It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below:       

·         The system should be able to interface with the existing system

·         The system should be accurate

·         The system should be better than the existing system

The existing system is completely dependent on the staff to perform all the duties.