Requirement Engineering Assignment - I
Student Information System
This overview is consisting of several sections identified as functional requirements, user requirements,system requirements, system design and finally software requirements specification.
Functional requirements are specification of a document written by statements in natural languagethat define a function of a software system or its component. The purpose of this section is to providea high-level functional description (FD) and to list the functional requirements definitions for the e-Enrolment system implementation. It will be updated after user requirements are specified in moredetail. Its main purpose is to describe the system functions to be satisfied and serves as a basis for amutual understanding between the stakeholders. It also provides information on the proposedmethods and procedures, and includes assumptions and constraints. As new functionality isconceived/implemented in the further phases, this section will be updated to describe those functionsand integrate them into the system.
User requirements are specification of a document written by statements in natural language plusdiagrams of the services the system provides and its operational constraints. It is written for customersand should describe functional and non-functional requirements in such a way that they areunderstandable by system users
who don’t have detailed technical knowledge.
System requirements are specification of a document realized by a process of gathering informationabout the proposed and existing systems and distilling the user and system requirements from thisinformation.
System design is a document used by system developers in order to define what is to be realized. Itcontains details of implementation, algorithms, database and system organization, interfacespecification etc. Sources of information for system requirements include documentation, systemstakeholders and the specifications of similar systems. The requirements themselves are thedescriptions of the system services and constraints that are generated during the requirementsengineering process.This requirements specification document will address
What is the software supposed to do?
How does the software interact with people, the system’s
hardware, otherhardware, and other software?
What is the speed, availability, response time, recovery time of various softwarefunctions, etc.?
Attributes - What are the portability, correctness, maintainability, security, etc. considerations?
Design constraints imposed on an implementation
Are there any required standards in effect,implementation language, policies for database integrity, resource limits, operating environment(s)etc.?