You are on page 1of 8

Requirement Specificatiom

Software requirements analysis is a process of discovery, refinement, modeling,


and specification. The system requirements and role allocated to softwareinitially
established by the system engineerare refined in detail. Models of the required data,
information and control flow, and operational behavior are created. Alternative solutions
are analyzed and a complete analysis model is created.

The correct system is that satisfied all users requirements therefore it is
very important to analyze the existing system and to document the software
requirement specification for proposed system, which in turn provides the base for
development of the proposed system.


Along with our technical training, we simultaneously started the system
study and analysis. During this phase, initially we started with studying the
system specification documents to understand the system and unveil the basic
system element involved.


Our project guide conducted a series of lectures to impart us the required
knowledge about the system. During the lectures, we also had question and answer
session at the end, which helped us have a clear idea about the expected system.

Interviewing :-

We had visited the Tapovan Vidhyalaya, Mr. Alpeshbhai Dhameliya is the
principal of the school. To meet and getting the correct information all the
document, records and database and proper working criteria of school website.
Information of the school existing system and requirement for proposed system.

Questionnaires


1) Why is the system required?
2) Which kind of extra functionality required?
3) What facilities must be supported by the proposed system?
4) How will the proposed system help?
5) Which types of system give better result?
6) Which kind of modules are required to design the system?
7) What are current process problems?
8) Is new technology needed? What skills?
9) How much they are familiar with the computer and in which
10) Language they will easily operate their system?
11) What if the system wasnt implemented?
12) Which are your other competitors?
13) Do they have their web site?
14) May I have the URLs of Web site of your competitors?

2.2 Feasibility Study
Once scope has been identified it is reasonable to ask, Can we build software to meet
this scope? Is the project feasible? Software feasibility has four solid dimensions.
1) Technology, Is project technically feasible?
2) Finance, Is a project financially feasible?
3) Time, Will the projects time-to-market beat the competition?
4) Resource does the organization have the resource needed to success?
The entire four dimensions are examined by answering the above questions. We realized that
answer to all those questions is possible & conducted that our project is feasible in our sense.
Following information gives the details of examination of entire four dimensions.
Technical Feasibility:
The S/W is technically feasible. The nature of the language in which we are building the
software is very supportive activities can be easily implemented. The defects can be easily
reduced to a level matching the applications needs to a level matching the applications needs.
The implementation is quite supportive.
As we are going to develop system for community portal using asp.net in our project, we
need proper knowledge of technology and its function areas. We should make sure that
functionalities specified in system could be achieved using this technology. We should refer to
other applications developed using this technology for better understanding. Books,
Documentation of technology provided by authors of technology and other resources on Internet
might help too much extend.
Finance:
Finance matters can restrict to the level of development. However our management is
assuring that any needs will be fulfilled immediately. The management has provided the
required resources. From the financial point of view the project is feasible. We guess there will
not be any bigger monetary requirement for our project.

Time Duration:
The critical dimension to Study is to analyze: will the current time to market beat the
competitions? The time period, in which our system will be launched into the market, the
competition will be higher as several existing system has already captured the market with their
valuable and satisfied services. However our study status that we will the competition as we
have done enhanced feature like uploading multiple files, chat, and send mail etc. Although we
will be having strong competition, we will try to give best services through excellent work &
research.
We have 5 months for developing entire system. It is sufficient time for developing such
application. We prepared time schedule that can efficient manage proper time required for
project work.
Resources:
We have enough resources to get our project success and complete it within time limit.
When developing any system, we need proper environment resources as well as manpower. For
developing .net application available application tools are enough and we can get it more from
internet. Also our team members are acquainted to such type of development environment. For
gathering more help when development application we also provision of an Internet connection.







































The Online Classified Portal project requires frequent user interaction. For that
reason, our first choice included the Prototype model. However, we had doubts about the
prototype model, and therefore we concluded to use the Spiral Model. The risk-based
approach of the Spiral Model is significant to the development of this prototype, and it would
also help select an established lifecycle model or determine a different model constructed
from various phases of other lifecycle models. After regular reviews, we decided that the best
approach was to use a hybrid model that would implement the risk management of the spiral
model along with the incremental model, which is a mixture of the prototype model and the
4.4 Life Cycle Model
linear sequential model. Currently, the project revolves around two established stages:
Requirement Analysis and Prototype Development. Above figure shows the life cycle for the
development process as well as entry and exit criteria for the different phases of the project.
























Project Planning: 2 to 3 %

Requirement Analysis: 10 to 25 %

Design: 20 to 25 %

Coding: 15 to 20 %

Testing / Debugging: 30 to 40 %


Testing and
Debugging
Analysis (30-40%)
And
Design
(40-50%)


Coding
(15-20 %)
4.5 Effort Distribution





































Delivery Confirmation


Requirements
Analysis
Requirements
Gathering
Estimation Scheduling
Testing
Coding &
Integrating
Module

Designing
4.6 Task Dependency Diagram
Timeline Chart

When Scheduling of a software project is done, the planner begins with a
set of tasks to be performed. If automated tools are used, the work breakdown is input
as a task network or task outline. Effort, duration and start date are then input for each
task. In addition, tasks may be assigned to specific individuals.

As a consequence of this input, a Timeline Chart also called a Gantt chart
is generated. A Gantt chart can be developed for the entire project as in our case my
entire project duration is of size months. Thus developing a Gantt Chart or Timeline
Chart for INTRANET COMMUNICATION MANGMENT SYSTEM of three months duration
which is as shown below.


Work Tasks Month 1 Month 2 Month 3
1. Identify needs and benefits
Meet with customers
Identify needs and project constraint
Establishment product statement
Milestone: Product statement defined
2. Define desired output / control/ input
Document OCI
FTR: Review OCI with customer
Revise OCI as required
Milestone: OCI defined
3. Front End Coding
Back End Coding
Validations
Milestone: Coding accomplished
4. Module Testing
System Testing
User Testing
Milestone: Testing accomplished
5. Implementations
User training
Milestone: Accomplished






















Fig 9.1.1


As per seen in the above Gantt chart, Project Tasks are listed in the left-
hand side column. The horizontal bars indicate the duration of each task. When multiple
bars occur at the same time on the calendar, task concurrency is implied. The diamonds
indicate milestones.