[NAME OF PROJECT] REQUIREMENTS SPECIFICATIONS

JULY 25, 2012 [Member 1 FamilyName,FirstName MI] [Name of Member 2] [Name of Member 3]
[Note: Arrange alphabetically according to family name]

Requirements Specifications

Chapter 1
1.1 Purpose

Introduction

(This subsection includes discussion on the purpose of developing the new system. It describes why the project is undertaken and its possible benefits when completed. Discussion must not be less than 50 words. Important: This is only the introduction part, you dont have to describe in details the functionalities of your software. Just describe in general what it can do and its benefits.)

1.2 Scope
(The scope discussion should identify the type of software product to be developed (e.g. Host DBMS, Report Generator, Games, Natural Language Translator, Algorithm Analysis, PIC-Based, Information Robotics, Expert System, etc.) describe the major functionalities of the project. Each of the functionality must be discussed separately. Please do not do a detailed discussion, two or three sentences will do. The detailed discussion must be done in Chapter 3.) System, Simulation,

1.3 Project Constraints and Limitations (Describe any organizational, security, and technological or other constraints under which this system must be developed or subject to. This is somewhat related to the List of Exclusion. You can do bulleting here but you need to discuss the limitations.). The product will only run in Linux system. The software only supports single user. The software has no network support. )

1.4 Hardware Requirements

(These are the minimum hardware requirements for the software or project to work properly. Example: At least 128 Kbytes of RAM * if pc based At least 20GB of hard disk * if pc based At least 2kB Program memory * if uC based At least 128B EEPROM * if uC based etc. )

1.5 Software Requirements

Requirements Specifications

(These are the minimum software requirements for the software or project to work properly. Is not applicable to CpE hardware projects.

Examples:

Windows XP * if pc based Java (specify the version) * if pc based MPASM * if uC based PICC * if uC based etc. )

1.6 Definitions of Terms

(This section provides important terms, acronyms and abbreviations used in the project. For example in a Game Project, there is a need to define important tools and technical game rules terms that are unfamiliar to ordinary users.)

1.7 References
(This subsection should provide a complete list of all resources used creation of the Requirements specifications Examples include books, websites, journals, etc. ) referenced in the

Requirements Specifications

[1]

Braude, Eric J.: Software Engineering: An Object Oriented Perspective, 5th Edition, McGraw-Hill, 2001, ISBN 0-073-65578-3 For books please follow the format above (please delete sample entries in #1): Author, title of the book in Italic format, edition, Publisher, Year Published and ISBN if applicable

[2]

[3] Venners, Bill. The Demand for Software Quality. Artima Software Inc. August 12, 2005. http://www.artima.com/intv/serious.html. [4] For internet references, please follow the format above (Please delete sample entries in #3): Author, Title of article in double quote and italic format, the company or publisher, date of publication and the URL. Please add more entries to your references as needed.

[5]

Requirements Specifications

Chapter 2

System Analysis

(This section should specify the logical requirements of the project. Use the appropriate modeling for your project. This may include Flowcharts Use Case Diagram Activity Diagram Class Diagrams ERD DFD etc.

Most of the modeling mentioned above is not applicable to CpE hardware projects. Please discuss with your adviser on how to document your system analysis.. It may include Block Diagram, Flowcharts and others as suggested by your adviser).

2.1 System or Software Architecture (identifies the major components of the system. Example: An OS architecture would include the file system, printing system, kernel, etc. For hardware projects, this is similar to a block diagram of the system. A discussion must follow to describe the interaction of the major components. )

2.2 Flowcharts (This includes the main flowchart of the system. Create the general flow of the system and then have a detailed flowchart for each functionality. You can have subsections to illustrate the flowcharts of the major functionalities. Please dont forget to discuss each flowchart. ) 2.2.1 2.2.2 Functionality 1 Flowchart Functionality 2 Flowchart

2.3 Data Flow Diagram (the succeeding sectioning is discretion of the Project Team. Please consult your adviser on this.)

2.4 Entity-Relationship Diagram

Requirements Specifications

Chapter 3

Functional Requirements

(This chapter is a detailed description of the major functionalities of the system. This will give an idea to the adviser and panel on what the software can do.)

3.1 Functionality 1 (describe the functionality in an inverted triangle style, meaning from general to specific. For sub-functionalities under the main functionality you can create sub-sections. Describe the purpose of each subfunctionality.)

3.1.1 3.1.2

Sub-functionality 1 (describe in detail the purpose of the functionality) Sub-functionality 2

3.2 Functionality 2

3.3 Functionality 3

3.4 Functionality 4

Chapter 4

User Interface/Physical Layout

This chapter is a general description on how the graphical user interface of the system works. On the software side, it describes the controls (menus, dialogs, buttons, radio buttons, etc.) to be used to implement all the functional requirements in Chapter 3. The projects which are more inclined to hardware will outline the design of your project prototype or layout. Example would be how the buttons, switches, sensors are positioned. Always include discussion after every diagram.)

4.1

Main User Interface (The main user interface is the first graphical user display when you run your software. It is advised that you already create this with the language that you are going to use. If not possible, find a way to simulate the GUI using any graphics software like Photoshop, Visual Studio, CAD etc. Have a short discussion after the main user interface.)

4.2

Control 1 (For the controls, you need to have a GUI display included. Just describe the purpose of the controls. For example, for the Menus you need to list down the Main Menus and create subsections for submenus. Relate each menu/submenu to the functionality describe in Chapter 3. 4.2.1 Sub-controls 1

4.2.2 Sub-controls 2 4.3 Control 2 (the sectioning depends on the controls you are using. It is your discretion what control to discuss in each section.) 4.4 Control 3

[Please follow the fonts use in this template and also the double spacing.]

Requirements Specifications

11