Html Css

Only available on StudyMode
  • Download(s) : 571
  • Published : February 23, 2011
Open Document
Text Preview
Student Course Registration System

REQUIREMENTS REPORT

CENG XXX Fall 2001

October xx, 20XX

Ayşe Güzel
Mehmet Güçlü

Computer Engineering Department
Middle East Technical University

Student Course Registration System

Requirements Analysis Report
date

1. Introduction
–1.1 Purpose of this Document
–1.2 Scope of this Document
–1.3 Overview
–1.4 Business Content
2. General Description
–2.1 Product Functions
–2.2 Similar System(s) Information
–2.3 User Characteristics
–2.4 User Problem Statement
–2.5 User Objectives
–2.6 General Constraints
3.Functional Requirements
Descriptions about what the system should accomplish – not how. 3.1 Registration {Top level functions are called: “Capability”} •Description about the top-level system function (Capability). •USE CASE DIAGRAM

3.1.1 Student Log-in {This is a “System Function”}
Corresponds to a USE CASE (one oval in the use case diagram) •Draw a COLLABORATION Diagram
Description paragraph.
Then comes numbered requirements: One sentence each!
3.1.1.1 Every student has a Username
3.1.1.2 Usernames are unique
IEEE suggests every requirement to come with (include only if appropriate): 1.Description
2.Criticality
3.Technical issues
4.Cost and schedule
5.Risks
6.Dependencies with other requirements
7.Others as appropriate

3.1.2 Student Authentication
4.Interface Requirements
4.1 User Interfaces
4.1.1 GUI {Screen Dumps}
4.1.2 Command Line Interface
4.1.3 Application Programming Int.
4.1.4 Diagnostic interface
4.2 Hardware Interfaces
4.3 Communications Interfaces
4.4Software Interfaces
5.Performance Requirements
6.Design Constraints
6.1 Standards Compliance
7.Other Non Functional Attributes
1.Security
2.Binary Compatibility
3.Reliability
4.Maintainability
5.Portability
6.Extensibility
7.Reusability
8.Appl. Affinity/compatibility
9.Resource Utilization
10.Serviceability
11. --- others ---
8.Preliminary Object-Oriented...
tracking img