Html Css

 Html Css Essay

College student Course Registration System

REQUIREMENTS REPORT

CENG XXX Fall season 2001

August xx, 20XX

Ayşe Güzel

Mehmet Güçlü

Computer Architectural Department

Central East Technological University

Student Course Enrollment System

Requirements Analysis Report

date

1 . Introduction

–1. 1 Purpose of this File

–1. two Scope on this Document

–1. 3 Summary

–1. some Business Content

2 . Basic Description

–2. 1 Merchandise Functions

–2. 2 Comparable System(s) Info

–2. several User Characteristics

–2. 5 User Difficulty Statement

–2. 5 Customer Objectives

–2. 6 Standard Constraints

three or more. Functional Requirements

Descriptions about what the system ought to accomplish – not just how. 3. 1 Registration Top level functions are called: "Capability” •Description about the top-level system function (Capability). •USE CASE PLAN

3. 1 . 1 Scholar Log-in This is a "System Function”

•Corresponds to a USE CIRCUMSTANCE (one oval in the employ case diagram) •Draw a COLLABORATION Picture

•Description section.

•Then comes numbered requirements: One sentence each!

several. 1 . 1 ) 1 Every single student provides a Username

a few. 1 . 1 . 2 A are exclusive

IEEE advises every necessity to have (include only when appropriate): 1 . Description

2 . Criticality

a few. Technical concerns

4. Expense and plan

5. Risks

6. Dependencies with other requirements

7. Others as appropriate

3. 1 ) 2 Pupil Authentication

4. Interface Requirements

4. one particular User Cadre

4. 1 . 1 GUI Screen Dumps

four. 1 . 2 Command Line Interface

four. 1 . three or more Application Encoding Int.

four. 1 . 5 Diagnostic interface

4. a couple of Hardware Cadre

4. three or more Communications Extremite

4. 4Software Interfaces

your five. Performance Requirements

6. Style Constraints

six. 1 Specifications Compliance

7. Other No Functional Attributes

1 . Secureness

2 . Binary Compatibility

three or more. Reliability

some. Maintainability

five. Portability

6. Extensibility

six. Reusability

8. Appl. Affinity/compatibility

9. Resource Utilization

15. Serviceability

10. --- other folks ---

eight. Preliminary Object-Oriented...

References: -- others --

{NOTE: Titles have to be written, even if there is nothing to write under}

Popular