SYSTEM ANALYSIS

The Software development life cycle is a common methodology for system development
in many organizations, featuring various phases that mark the progress of the system analysis
and design effort
System Analysis and Design, is the process of gathering and interpreting facts, diagnosing
problem and using the information to recommend improvement to the system. Before development of
any project can be pursued, a system study is conducted to learn the details of the current business
solution. Information gathered through the study forms the basis for creating alternative design
strategies.

Virtually all organizations are systems that interact with their environment through

receiving input and producing output.

Project Initiation and Planning:

The requirement specification for developing the project was analysed in this stage. The
requirements include software requirement, hardware requirement and labor requirement. This
was finalized by the project leader along with the team.
Project Analysis:
The project was analysed to see whether ant modules in the project were already
available to be reused so as to save time and work. The over all development time for the project
was also analysed. In addition, the number of modules and number of programmers required
were also analysed and finalized. This was finalized by the project leader along with the team.

Logical and Physical Design:

As already mentioned the team consists of three members, two programmers and one
designer. The designer along with the team designed the look and feel of the project. It presents a
very friendly user interface. The layouts have been designed in such a way that there is minimum
direct input and more of choice input. After finalizing the design, the project was uploaded into
the Demo Server and the URL was given to the client.
Maintenance
Verification with Client:
The design is checked with the client for his satisfaction . After his approval the project is
taken to the next phase. If the client is not satisfied, alterations are made according to the clients
suggestions.

Briefing the Project into Modules:

After the client approval, the project is divided into modules and the modules are
assigned to programmers. The timeframe for the module completion is also given. This will be
finalized by the project leader along with the team. The programmers are also given instruction
about naming the common files and folders. This was a very sensitive phase and so the modules
were planned perfectly and assigned to programmers.

Database Design:
Database design was the backbone for this project. The database for this project was
designed to the requirements keeping in mind the constraints and easy of use. A total of eleven
tables were designed for this project strictly to be flexible and can therefore support any level of
expansion and customized.

Coding:
The coding for different modules was developed keeping in mind the commonality
between modules. Common files and folders were used for avoiding repetition of code.

Testing:
The testing process was usually done manually by a tester. The process involves repeated
testing of the project until all the bugs are fixed. This process may take several phases until the
project is clear of bugs. A testing report, usually in an Excel sheet is submitted to the
programmer by the tester.

The programmer fixes all bugs and again the testing phase is continued. This process is
repeated until all bugs are cleared. At last the project is verified by the project leaders to see
whether all requirements are met.

Maintenance:
The maintenance for this project is done for six months. A good product must be able to
incorporate future modification and enhancement. Throughout the maintenance phase changes
keep cropping up and the portal must be able to adjust itself to the changing situations. The
portal has been developed keeping this in mind.