Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
RE - Assign - I

RE - Assign - I

|Views: 2|Likes:
Published by Iqbal Uddin Khan
Requirement Engineering - Assignment - I, by Engr Kashif Abbasi
Requirement Engineering - Assignment - I, by Engr Kashif Abbasi

More info:

Categories:Types, School Work
Published by: Iqbal Uddin Khan on Feb 08, 2013
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Assignment - I
Iqbal Uddin Khan
Requirement Engineering
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?
External interfaces
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.?
Requirement Engineering
The main purpose of system requirements is to specify a document that can be used by three groups:
Those who design (system designers),
Those who decide (managers), and
Those who develop/realize (system developers).
General overview
The student information system should automate the overall inter institute processes of the Campus. Thesystem should organize student data, employees, and study programs, various data about the educationalpr
ocess and the faculty’s research and scientific work. The system
should automate the work of the studentservice, human resources management, schedule of lectures, management of student payments on variousgrounds, distribution of resources (professors and classrooms), organization of online services for the studentsand various other activities.The main objective of this project is to implement a Students information system. The integrated informationsystem for the university ought to achieve numerous enhancements:
Fast and efficient administration
Quality of the services provided to the students
Engagement of the faculty staff in administering the data and information
Accurate and updated data for the University and the faculties
High quality, continuous and instant access to the faculty and university data.
General overview
All rules related to the business logic should easily be defined without changes to the application (for instancemin/max number of transferred credits). Every change made in the system by the users should be recordedlogged. The log can later be used to see who, when and from where made changes in the database. Thesystem should have an intuitive user interface where a simple procedure with the fewest steps possible willenable completing the required tasks.The user interface
the use of all components of the system by the: faculty members, associates, studentsand potential students should be only through a WEB interface. The WEB should use modern technologiesthat will bring fast response with small burden on the server by doing most of the validation process on theclient side. All user forms should have fast access to on-line help, context dependent. The components used bythe system administrator or office users can be implemented as standalone desktop applications or WEBapplications. Additional possibilities for an additional web interface for small devices (PDA, mobile phones)should be planned.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->