Software Requirements Specification

Vietnamese-German University
Software Requirements
Specification
Version 1.1
By Richard Bradley, MAL, MSM

(note to students this is the cover for the sample report it is not part of the report)
November 2013
This document provides guidance for the formatting and organization of Software
Requirements Specifications (SRS) to students of the Vietnamese-German University of Vietnam,
who are taking the class English for Computer Science. The software requirement statement
students are expected to prepare for this course is based on the industry standard Software
Requirements Specification and is intended to provide students with an introduction to the
fundamentals of technical writing for Computer Science engineers.
This guide should not be considered as a rigid requirement, but more as a set of suggestions
on how students can organize their Software Requirements Specifications. The examples presented
in this guide are neither to be considered as complete nor as absolutely required, but are provided to
give an idea of the kind of information that would appear in the different sections. Students will
need to provide more details in many of the sections, additional sections may need to be added and
some sections may be eliminated, depending on the particular requirements of the system being
proposed.
While every effort has been made to insure the accuracy of this document, if you notice any
errors, please bring them to the attention of the Course Instructor.
Richard G. Bradley, MAL, MSM
Course Instructor
Change Log
Date
Change
Reason
5 Mar All references to Software Proposal were changed to

2012 Software Requirements Specification.
Reduce confusion, use

standard name
29
Nov
2013
Reports are done in

teams and CS students
needed an example
EEIT changed to CS. Content changed to reflect multi-member

teams instead of single author
(Note to students: Don't include this page in your report either. The cover sheet labels on the next
page should be your first page)
(cover sheet)
(Label should be about 1/3 down the page)
Robocreams menu
Version 1.0
Software Requirements Specification

<student name>
English for Computer Science
Vietnamese-German University
<due date>
(Page intentionally left blank)
(Letter of Transmittal)
(Begin 1 line 2.m from top of paper or after 1 blank line after Letterhead)
st
<student name>
<student number>
Class <class number>
<date>
(1 blank line)
<Instructor>.
Vietnamese German University
Foundation Year Studies
Nam K Khi Ngha Street, Ha Ph District
Bnh Dng New City, Bnh Dng Province
(1 blank line)
Dear Mr.Richard Bradley, MAL, MSM
(1 blank line)
Enclosed is our Software Requirements Specification for our class project entitled <proposal
name> submitted to partially meet the requirements for The CS2015 class.
This Software Requirements Specification discusses the context for the project, gives an overview
of what is to be produced, provides justification for the development of the software, addresses the
feasibility of the project and include a development schedule in the form of a Gantt chart.
I appreciate the time you are taking to review this Software Requirements Specification and hope
that it meets your and the boards approval so that we may go ahead and build and evaluate the
prototype. If you have any more questions feel free to contact me either by telephone <telephone
number> or e-mail: <email address>.
(1 blank line)
Sincerely yours,
(3 blank lines)
<Student Name>
Team Leader
(1 blank line)
Enclosure:<name of proposal>(1 Copy)
(Page intentionally left blank)
(title page)
The Vietnamese-German University

(20 pt Times New Roman)

Software Requirements Specification

for
Robocreams menu
Version 1.0
(24 pt Times New Roman, bold)
L Hong Qun
Phan Gia Thnh
Phm Th Thanh Tho
Instructor: Mr.Richard Bradley, MAL, MSM

Due date: 14/01/2016
(disclaimer)
Disclaimer
(18pt Times New Roman, bold)
(This is a boilerplate requirement. Type it exactly as it is written below and sign it.)
We declare that this Software Requirements Specification is a product of our own work,
unless otherwise referenced. We also declare that all opinions, results, conclusions and
recommendations are our own and may not represent the policies or opinions of the
Vietnamese-German University.
<Student Name>
<Student Name>
<Student Name>
Abstract
(Heading 1, 18 pt Times New Roman, bold)
Robocreams menu, Version 1.0

Le Hoang Quan
(The Abstract is an informative summary of, written after the Software Requirements Specification is
completed, that briefly describes the purpose, scope, background, overview of the system, conclusions
and recommendations. The abstract must be complete enough that it can be comprehensible even
after being separated from the described document and include keywords that will allow this
document to be located when put into a database system..)
(Discuss the environment that the software is expected to function in and the justification for its
development.)
The purpose of the Robocreams menu, Version 1.0 project is to create a working
online menu for an ice-cream/cafe store named Robocream. The project is expected to replace the
traditional paper menu that has become obsolete and inconvenient according to todays standard.
(Briefly describe the proposed system.)
Robocreams menu, Version 1.0 will consist of a web-based client interface. The
websites users will have access to all of the websites contents which includes Robocreams
history, products, prices, events, the design teams information and e-mail. However, in order to
change those information, the user must have the admins privilege. The user can gain access to this
privilege by logging in the admin page with an account that is circulated internally. The web pages
have been created using HTML 3.2 and use Javascript for some functions. Client requirements are
minimal, any modern browser will be sufficient and the website can be hosted on a server can with
512MB of memory and a 2592 MHz Intel Model 2 CPU or better.
Key words: topic, client, server, SQL, VGU, circulated internally
ii
Acknowledgements
(Acknowledge anyone who assisted you)
We would like to express my deep appreciation to the lecturers of the Vietnamese-German
University for their explanations and guidance
We would also like to thank all my friends and classmates for their suggestions and assistance
during the writing of this Software Requirements Specification.
During the creation of this report:
Le Hoang Quan was responsible for writing reports, drawing the development plan and
offering some minor assistance in the coding process.
Pham Thi Thanh Thao was responsible for preparing presentations, drawing the websites
sketch, coding the menu pages, the admin function and designing the look of the website.
Phan Gia Thinh was responsible for designing and coding the index page (homepage),
providing some useful softwares for the design process.
Le Hoang Quan
iii
Table of Contents
Disclaimer.............................................................................................................................................1
Abstract.................................................................................................................................................2
Acknowledgements..............................................................................................................................4
Table of Contents..................................................................................................................................5
List of Figures.......................................................................................................................................7
List of Tables........................................................................................................................................7
1.Introduction.......................................................................................................................................1
1.1.Purpose (heading 2, 14 pt,Times New Roman, bold)................................................................1
1.2.Audience....................................................................................................................................1
1.3.Project Scope.............................................................................................................................1
1.4.Overview of the Document........................................................................................................2
2.Context of the Project........................................................................................................................3
2.1.Background................................................................................................................................3
2.2.Current System...........................................................................................................................3
3.Overview of the Proposed System....................................................................................................5
3.1.Description.................................................................................................................................5
3.2.Product Features ........................................................................................................................5
3.2.1.Login (heading3, Times New Roman, bold).......................................................................5
3.2.2.Administrators Menu..........................................................................................................5
3.2.2.1.Create new users...............................................................................................................6
3.2.2.2.Delete users......................................................................................................................6
3.2.2.3.Modify user information...................................................................................................6
3.2.2.4.List topics by submitted date, Student ID or Student name.............................................6
3.2.2.5.Review submissions and Approve/Disapprove topics......................................................6
3.2.3.Users Menu.........................................................................................................................6
3.2.3.1.Terms and Conditions.......................................................................................................7
3.2.3.2.Modify Personal Data.......................................................................................................7
3.2.3.3.List topics by submitted date, Student ID or Student name.............................................7
3.2.3.4.Submit a topic for approval..............................................................................................7
3.3.User Classes...............................................................................................................................7
3.3.1.Instructor..............................................................................................................................7
3.3.2.Users....................................................................................................................................7
3.4.Operating Environment..............................................................................................................8
3.4.1.Hardware Platform..............................................................................................................8
3.5.Design and Implementation Constraints....................................................................................8
3.5.1.Software Constraints...........................................................................................................8
3.5.2.Database Constraints...........................................................................................................8
3.6.User Documentation..................................................................................................................9
3.6.1.Administrator Manual.........................................................................................................9
3.6.2.User Manual........................................................................................................................9
3.6.3.On-Line Help.......................................................................................................................9
3.7.Assumptions and Dependencies................................................................................................9
3.7.1.Assumptions........................................................................................................................9
3.7.2.Dependencies.....................................................................................................................10
4.External Interface Requirements.....................................................................................................11
4.1.User Interfaces.........................................................................................................................11
4.1.1.HTML Standard.................................................................................................................11
4.2.Hardware Interfaces.................................................................................................................13
iv
4.3.Software Interfaces..................................................................................................................13
4.4.Communications Interfaces.....................................................................................................13
5.Conclusion.......................................................................................................................................15
6.Recommendations...........................................................................................................................16
7. References......................................................................................................................................17
Appendix A: Glossary of Terms...........................................................................................................1
Appendix B, Gantt Chart......................................................................................................................1
Appendix C: Software Design Diagram...............................................................................................1
Cover page.....................................................................................................................1
I. User Admin.................................................................................................................1
II. Review, Approve, Disapprove Topics.......................................................................1
Exit.................................................................................................................................1
Terms and Conditions....................................................................................................1
I. User Admin.................................................................................................................1
II. Topics........................................................................................................................1
Exit.................................................................................................................................1
Appendix D: Database Elements..........................................................................................................1
Appendix E: Screen Images.................................................................................................................1
E.1 Login Screen..............................................................................................................................1
E.2 Administrator Menu and First Screen........................................................................................2
Cover page.....................................................................................................................2
I. User Admin.................................................................................................................2
Exit.................................................................................................................................2
E.3 Create Users...............................................................................................................................3
Cover page.....................................................................................................................3
I. User Admin.................................................................................................................3
Exit.................................................................................................................................3
E.4 Delete Users...............................................................................................................................4
Cover page.....................................................................................................................4
I. User Admin.................................................................................................................4
Exit.................................................................................................................................4
E.5 Select User to Modify................................................................................................................5
Cover page.....................................................................................................................5
I. User Admin.................................................................................................................5
Exit.................................................................................................................................5
E.6 Modify Personal Information....................................................................................................6
Cover page.....................................................................................................................6
I. User Admin.................................................................................................................6
Exit.................................................................................................................................6
E.7 Topics Sorted by Date Submitted..............................................................................................7
Cover page.....................................................................................................................7
I. User Admin.................................................................................................................7
Exit.................................................................................................................................7
E.8 User Menu and First Screen......................................................................................................8
Terms and Conditions....................................................................................................8
I. User Admin.................................................................................................................8
v
II. Topics........................................................................................................................8
Exit.................................................................................................................................8
List of Figures
Figure 1 Context diagram for release 1.0 of the Report Topic Database System.................................5
Figure 2 Standard Header...................................................................................................................11
Figure 3 Software Menu Module Overview.........................................................................................1
List of Tables
Table 1 Database Elements...................................................................................................................1
vi
1. Introduction
1.1.
Purpose (heading 2, 14 pt,Times New Roman, bold)
(Reference the source of the information about the project, Identify what follows as a Software Requirements
Specification, identify the product to be specified in this document, including the revision or release number,
give an overview of the contents and specify who is the intended audience. Note that this subsection does not
describe the project.)
This Software Requirements Specification for the ice-cream/cafe store Robocreams online
menu is submitted for partial fulfillment of the requirements of the course English for Computer
Science at the Vietnamese-German University and includes an overall description and listing of the
software functional and nonfunctional requirements for the project. Unless otherwise noted, all
requirements specified here are high priority and committed for release 1.0.
1.2. Audience
(Whom is this document written for?)
The intended audience of this document is the potential customers of Robocream, who will use
this website to see the palours products, services and events in order to decide if they want to use
Robocreams products or not.
1.3. Project Scope

(Provide a short description of the software being specified and its purpose, including relevant benefits,
objectives, and goals.)
The menu for Robocream will provide the customer with neccessary information about
robocream, such as availble products, upcoming products and events, robot and services,... The
website will be easy for the customer to navigate and search for informations. There will be some
effects but the website wont rely on them a lot as they may decrease the websites compability. If
the website is done well, it may bring a great deal of profit for Robocream and improve the palours
popularity.
1.4. Overview of the Document

(Describe the contents and organization of the rest of this document. Since there is already a Table of Contents,
this overview will be less formal but more informative. Describe the two basic remaining sections, the Overall
Description and the Requirements Specification.)
This document provides the scope and context of the project to be undertaken, including the
background, feasibility, basic requirements for this project, and justification for it implementation. It
also specifies the user interface, presents an overall description and details the intended user groups
and the value that the system will have to them, and provides a schedule for the completion of the
project, including a list of all the deliverables and presentations required.
2. Context of the Project

2.1. Background
(This section will discuss the background of the project and demonstrate that you have a good understanding
of the environment it will be operating in.)
Robocream is a newly opened automated Cafe/Ice-cream palor with robot waiters founded by
the billionaire Diego Maradona. In order to expand its popularity, Robocream needs an online
menu. The online menu let customers choose what to buy before coming to Robocream. The
website can be considered as the face of Robocream so if done well, it will attract alot of customers.
2.2. Current System

(Describe the current system and the reason it needs to be replaced.)
The current system is primarily a manual system which Robocreams customers choose the
products they want to buy on a menu sheet then order them through a robot waiter.
Limitations of the current system include:
Customers wont be able to preview Robocreams products without coming to the palour,
which is very inconvenient.
Its too primitive in this day and age, especially for an ice-cream/cafe store with robot waiters.
Customers wont be able to check Robocreams events without co ming to the store.
3. Overview of the Proposed System

3.1. Description
(This section gives an overview of the functionality of the project. It needs to be readable by the users of the
project so that they can be assured that the correct project is being designed.)
The proposed Robocreams menu, version 1.0 will be a new system, replacing the current
manual method. The system will consist of a web-based front end tied to a SQL database. The
system consists of an Index page that acts as the homepage, several Menu and Our Story pages
contain information about Robocream and its products and the Admin page which is the only way
to manage and change the systems source code. The Admin page can only be accessed by those
who have a special account that is for internal circulation only. The context diagram in figure 1
illustrates the external entities and system interfaces for release 1.0.
Figure 1 Context diagram for release 1.0 of the Report Topic Database System
3.2. Product Features

(Provide a high level summary of the major features the product and the significant functions that it
performs or lets the user perform. Organize the functions to make them understandable to any reader.)
The Robocreams menu will consist of a series of modals which the users will access via a series
of menus. See Appendix C for an overview diagram of the system.
4
3.2.1. Login (heading3, Times New Roman, bold)

When an user access the page, they can choose to login to the Admin page through a login button
on the corner of the screen. In order to be able to login, the user must have an account that consists
of an username and a password. There are only a few accounts available which are given to
trustworthy people.
3.2.2. Dynamic Contents
The contents of the web page can change according to the time the user access the page. For
example, if the user access the website in the morning, there will be a Good Morning message.
The website will also the date it was last modified.
3.3.3. Mail for Admin
3.3. User Classes

(Identify the various classes of users that you anticipate will use this system. Specify what their functions will
be, security or privilege level, and training requirements.)
3.3.1. Administrator
The Administrator can gain access to administrative privilege through an internally circulated
account. With this privilege he/she will be able to make changes to the source code, which in turn
changes the websites structure and information. The administrator is responsible for debugging the
website and updating it regularly.
3.3.2. Users
Robocreams customers will be able to log in to the system as common users and gain access to
all of the information in the system, but arent able to change them.
3.4. Operating Environment

(Describe the environment in which the software will operate, including the hardware platform, operating
system and versions, and any other software components or applications with which it must peacefully
coexist.)
3.4.1. Hardware Platform

The Robocream project must run on an IBM-Compatible PC with 512 MB of Total Physical
Memory, 2592 MHz Intel Model 2 CPU, and an 800 x 600 resolution color monitor.
3.4.2. Operating System
Microsoft Windows XP Professional, Service Pack 2.
3.4.3. Browser
Internet Explorer Version 7 or newer.
3.5. Design and Implementation Constraints

(Describe any items or issues that will limit the options available to the developers. These might include:
corporate or regulatory policies; hardware limitations (timing requirements, memory requirements);
interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations;
language requirements; communications protocols; security considerations; design conventions or
programming standards. )
3.5.1. Software Constraints

Notepad and Microsoft SQL Server 7.0 must be used to develop and maintain this
system.
3.5.2. Database Constraints
In order to allow for import of data from the university record system and future expansion of
this system, all data elements for personal information must conform to those currently being used
by the University Student Records system. (See Appendix D for Database Elements)
3.6. User Documentation

(List the user documentation components (such as user manuals, on-line help, and tutorials) that will be
delivered along with the software. Identify any known user documentation delivery formats or standards.)
The administrator will be provided with a short administrator manual that describes how to login
to the Admin page along with the account.
3.7. Assumptions and Dependencies

(List any assumed factors (as opposed to known facts) that could affect the development of the software.
These could include third-party or commercial components that you plan to use, issues around the
development or operating environment, or constraints. The project could be affected if these assumptions are
incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such
as software components that you intend to reuse from another project, unless they are already documented
elsewhere.)
3.7.1. Assumptions
During the development of this Software Requirements Specification the following assumptions
were made:
The administrator will be computer literate, able to perform simple administrative tasks.
The SQL database system will be managed by a trained administrator able to maintain the
system.
3.7.2. Dependencies
Successful implementation is contingent on the following factors:
Availability of space on the university servers to host the database.
Support by the university Computer Science staff.
4. External Interface Requirements

4.1. User Interfaces
(Describe the logical characteristics of each interface between the software product and the users. Include
sample screen images, any GUI standards or product family style guides that are to be followed, screen
layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard
shortcuts, error message display standards, and so on.)
4.1.1. HTML Standard

Web pages will be coded using HTML 3.2 standards, as specified by The World Wide Web
consortium (W3C) and the Style Guide for Web Pages.
4.1.2. Page Layout
All pages, with the exception of the login page, will be organized into frames as follows:
a header (top section, 110 pixels in height, running the width of the page)
a center section divided into two parts (variable height, using rest of page)
a navigation bar (middle left section, 20% of width)
a contents section (middle right section, 80% of width)
and a footer (bottom section, 70 pixels in height, running the width of the page).
4.1.3. Header
The header or banner section will be an invisible table divided into three parts (25%, 50%,
25%) as follows:
On the left: The Vietnamese-German University logo (116 x 55 pixels)
In the center with <small> font

On the right: blank

Figure 2 Standard Header

8
4.1.4. Navigation Bar

The navigation bar will display a hyperlinked menu with the following selections:
Administrator Menu (see E.2 for an example)

Cover page
I. User Admin
1. Create Users
2. Delete Users
3. Modify Users
II. Review, Approve, Disapprove Topics
1. Topics by Submitted Date
2. Topics by Student ID
3. Topics by Student Name
Exit
User Menu (see E.8 for an example)

I. User Admin
1. Modify Personal Data
II. Topics
4. Submit Topic
Exit
4.1.5. Contents Screen

The contents screen will display screens the user selects from the menu.
4.1.6. Footer
The footer section will contain the following information
Questions and Comments (This will be a hyperlink to the webmasters email address)
Copyright 2015: The Vietnamese-German University (This will have a hyperlink to the home
page of the Vietnamese-German University)
Page last modified: <date> (This will show the last modified date of the document in the
contents window)
4.2. Hardware Interfaces

(Describe the logical and physical characteristics of each interface between the software product and the
hardware components of the system. This may include the supported device types, the nature of the data and
control interactions between the software and the hardware, and communication protocols to be used.)
The Robocream project does not make use of any direct hardware interfaces and will only use
the windows operating system to communicate with hardware devices
4.3. Software Interfaces

(Describe the connections between this product and other specific software components.)
The Robocream project will use client-server architecture. The client element will interface with
the user via an HTML interface. The server portion will consist of a SQL database running on a
university server.
4.4. Communications Interfaces

(Describe the requirements associated with any communications functions required by this product,
including e-mail, web browser, network server communications protocols, electronic forms, and so on.)
4.4.1. TCP/IP
The Robocream project will use the TCP/IP protocol suite, version 6 as implemented by
Microsoft .
4.4.2. Web Browser
10
The Robocream project client interface will run on Firefox 3.0 or Internet Explorer 7.0 or
higher.
4.4.3. Web Browser

The Robocream project will be programmed with HTML and Javascript.
11
5. Conclusion
(The concluding chapter will include a summary of the preceding chapters and any conclusions drawn. Do
not introduce any new material in this section. )
The Robocreams menu, version 1.0 describes a simple to use, client-server system that uses a
web-based client interface linked to a server hosted SQL database, which will replace the existing
manual system. This system will allow users to access to Robocreams information, products,
events, prices. The contents and structure of the website can only be altered through an Admin page.
If done right, the project will boost Robocreams popularity and create some good word of mouth
from the users.
12
6. Recommendations
The Robocream project should be developed initially as a stand-alone system with the ability to
supply Robocreams guests with the information they need. Future developments should include
the followings:
A forum where users can state their opinions about Robocreams products and services
and discuss about its events.
A register and login system for users. Any user with an account can comment on the
products on the website and rate them. This means that the will also be a system and a
rating system.
13
7. References
(List here any references to other documents cited anywhere in this document including references to
related project documents. Follow the IEEE format specified in the Style Guide for Engineering
Reports. You should have at least five references.)
[1] About the Vietnamese-German University, TPHCM, VN:VGU 2012 [Online] available:
http://www.vgu.edu.vn/university/. [Accessed Jan. 30, 2012].
[2] The Study Preparation Course: Foundation Year, TPHCM, VN:VGU 2012 [Online] available:
http://www.vgu.edu.vn/studies/bachelor/fy/. [Accessed Oct. 10, 2012].
[3] R. Bradley, Syllabus: English for Computer Science, The Vietnamese-German University,
TPHCM, VN:VGU 2012.
[4] W3C, HTML 3.2 Reference Specification; W3C Recommendation 14-Jan-1997
The World Wide Web consortium (W3C), 1999 [Online] available:
http://www.w3.org/MarkUp/Wilbur/ [Accessed Oct. 22, 2008].
[5] R. Bradley, Style Guide for Web pages, The Vietnamese-German University, TPHCM, VN:VGU
2012.
[6] Microsoft, Introduction to IP Version 6, Redmond: Microsoft Corporation. Published: Sept.,
2003, Updated: Jan. 11, 2008 [Online] available: http://technet.microsoft.com/enus/library/bb726944.aspx [Accessed Jan. 5, 2009].
14
Appendix A: Glossary of Terms

(Define all of the technical terms used in this document, including acronyms and abbreviations. Do not
assume the experience or expertise of the reader. Each type of reader will have a technical vocabulary not
necessarily shared by other readers.)
Client
SQL
VGU
Server
Circulated
internally
Term
Term
Term
Term
Term
Term
Term
A customer
Structured Query Language, a type of programming language
The Vietnamese German University
A computer or device on a network that manages network
resources.
Only for people in the company
Definition
Definition
Definition
Definition
Definition
Definition
Definition
A-1
Appendix B, Gantt Chart

(Gantt
chart showing your planned schedule for work on the phases of the project.)
Robocreams menu, Version 1.0
Status Date: 11 January 2016
Due Date: 14 January 2016
ACTIVITY
%COMPLETE
STATUS
Initial Proposal
100%
Analysis
100%
Database Design
80%
Interfaces design
60%
Coding
40%
Module Testing
25%
Implementation
10%
Date Ending
02/03/12
09/03/12
16/03/12
23/03/12
30/03/12
06/04/12
SSSS
SSSSS SSXX
BBSSSSS SSSX
SSSSSS SS
BSSSSS
BBB
SSSSS
BBBBB
S SSSSSS
Gantt chart Symbols
Deliverable Due Date
Project Status Symbols Planning/Progress Symbols
Initial Proposal
S Scheduled
B Work Before Schedule Time
Software Requirements Specification 02/03/12
A Completed
S Scheduled Activity Time
Prototype Web Site
23/03/12
C Caution
X Scheduled But not Worked
Test Plan
16/03/12
F Critical
X Scheduled But not Worked
Reference Manual
30/03/12
B-1
24/02/12
Appendix C: Software Design Diagram

Login
User Type
Admin Menu
Student Menu
Cover page
I. User Admin
Terms and Conditions

I. User Admin
1. Create User
2. Delete User
3. Modify User

II. Topics
1. Topics by Submitted
Date
3. Topics by Student
Name
4. Submit Topic
II. Review, Approve, Disapprove

Topics
1. Topics by Submitted
Date
3. Topics by Student
Name
Exit
Exit
Figure 3 Software Menu Module Overview
C-1
Appendix D: Database Elements

Table 1 Database Elements
Element
Family Name
Personal Name
Student ID #
Student Sex
School/Department
Student Class #
Password
Topic Title
Abstract
Read Plagiarism?
Approved/Disapproved
Reason Disapproved
Size
30
15
8
1
50
6
10
50
2000
1
1
15
D-1
Type
Text
Text
Text
Binary (M/F)
Text List
Text
Encrypted
Text
Text
Binary (Y/N)
Binary (Y/N)
Text - List
Appendix E: Screen Images

E.1 Login Screen
Help
Good Afternoon!
Today is 30 March 2012
Welcome To
The Report Topics Database System (RTDS)
Version 1.0
Username:
Password
Login
L og in
usernam e
Reset
Res et
Questions and Comments

Copyright 2012: The Vietnamese-German University
Page last modified 23 February 2012
E-1
E.2 Administrator Menu and First Screen

Cover page
I. User Admin
Help
The Report Topics Database System, Version 1.0

Admin Menu
1. Create Users
2. Delete Users
3. Modify Users
Good Afternoon!
II. Review, Approve, Disapprove

Topics
January 2009
S

10
11 12 13 14 15 16
17
18 19 20 21 22 23
24
25 26 27 28 29 30
31
Exit

E-2
E.3 Create Users

Create New User
Cover page
I. User Admin
1. Create Users
2. Delete Users
3. Modify Users
II.
Review, Approve,
Topics
Disapprove

Student's Surname:
Student's Given Names:
Student's Number:
Student's Sex:
Student's Department:
Student's Class Number:
Student's Password (10 char)
Male
Female
Com put erSc ienc ean dEn gine ering y
**** **
If you are sure that all you data is correct, click on the submit button
Submit
Reset
Exit
Sub mit mo d ife d da ta
Re set the fo rm bac kto or ign al

E-3
Help
E.4 Delete Users

Delete Users
Cover page
I. User Admin
Check to
delete
1. Create User
2. Delete User
3. Modify User
II.
Review, Approve,
Topics
Student
ID Number
Student
Name
Anh Duong
EEUN9999
Nguyen Thi Kim IUUN9999

Disapprove

Sung Yen
IUUN9998
If you are certain you want to delete the checked user, click on the Delete button.
Click on the Reset button to undo all of the checks.
Delete
Reset
De le te Ch ec ke dUs er s
Re se th efo rm ba ck to ori gina l
Exit

E-4
Help
E.5 Select User to Modify

Modify Users
Cover page
I. User Admin
Click on the number next to the name to open a screen to modify that user's account
1. Create User
2. Delete User
3. Modify User
II.
Review, Approve,
Topics
Disapprove

Student
Name
Student
ID Number
Anh Duong
EEUN9999
Nguyen Thi Kim
IUUN9999
Sung Yen
IUUN9998
Exit

E-5
Help
E.6 Modify Personal Information

Modify Personal Information
Cover page
I. User Admin
II.
Review, Approve,
Topics
Student's Surname:
Student's Given Names:
Student's Number:
Student's Sex:
Male
Female
Student's Department:
Student's Class Number:
Student's Password (10 char)
If you are sure that all you data is correct, click on the submit button
Submit
Reset
Ki m
1. Create User
2. Delete User
3. Modify User
Anh Ng uy en
ITUN9999
Disapprove

Exit
Com put erSc ienc ean dEn gine ering y
IT9999
**** **
Sub mitmo dif ied d at a
Re set the fo rm bac kto or ign al

E-6
Help
E.7 Topics Sorted by Date Submitted

Topics Sorted by Date Submitted
Cover page
I. User Admin
1. Create User
2. Delete User
3. Modify User
II.
Review, Approve,
Topics

Exit
Student
Name
Student
ID Number
Topic
Nguyen
Thi Kim
VGU9999
Report Topic
Database System
10/01/2012
Yes
11/01/2012
Sung Yen
VGU9998
Report Topic
Database System
11/01/2012
No
11/01/2012
VGU9997
Solar Powered
Bicycle
13/01/2012
Yes
14/01/2012
Disapprove
3 Anh Duong
4
5

E-7
Date
Approved
Submitted Yes/No
Help
Date
Approve/Reject
Reason
Duplicate
E.8 User Menu and First Screen


I. User Admin

II. Topics
1.
2.
3.
4.
Exit
Topics by Submitted Date

Topics by Student ID
Topics by Student Name
Submit Topic
Help
Use of this system constitute acceptance of the following terms and conditions:
1. All material and ideas submitted during the course become the property of the Vietnamese-German
University and can be used by the Vietnamese-German University for non-commercial activities.
2. All of the material provided by the instructor during this course are the property of the VietnameseGerman University and cannot be used for commercial purposes without the prior written consent of the
Vietnamese-German University and the author of the work.
3. Plagiarism: It is an Academic Offence to commit any act whereby a person seeks to obtain for
himself/herself, or for another, an unauthorized advantage with a view to achieving a higher mark or grade
than his/her abilities would otherwise secure. The substantial use of other peoples work and the
submission of it as though it were ones own is regarded as plagiarism. Work which is not undertaken in an
Examination Room under the supervision of an invigilator (such as dissertations, essays, project work
experiments, observations, specimen collecting, and other similar work), but which is nevertheless
required work forming part of the degree, diploma or certificate assessment, must be the candidates own,
and must not contain any plagiarized material.

E-8
E-9

Software Requirements Specification

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Software Requirements Specification

Încărcat de

Drepturi de autor:

Formate disponibile

Vietnamese-German University

By Richard Bradley, MAL, MSM

5 Mar All references to Software Proposal were changed to

Reduce confusion, use

Reports are done in

EEIT changed to CS. Content changed to reflect multi-member

Software Requirements Specification

(Page intentionally left blank)

(Page intentionally left blank)

The Vietnamese-German University

English for Computer Science

Software Requirements Specification

Instructor: Mr.Richard Bradley, MAL, MSM

Robocreams menu, Version 1.0

Purpose (heading 2, 14 pt,Times New Roman, bold)

1.3. Project Scope

1.4. Overview of the Document

2. Context of the Project

2.2. Current System

3. Overview of the Proposed System

3.2. Product Features

3.2.1. Login (heading3, Times New Roman, bold)

3.3. User Classes

3.4. Operating Environment

3.4.1. Hardware Platform

3.5. Design and Implementation Constraints

3.5.1. Software Constraints

3.6. User Documentation

3.7. Assumptions and Dependencies

Availability of space on the university servers to host the database.

Support by the university Computer Science staff.

4. External Interface Requirements

4.1.1. HTML Standard

a navigation bar (middle left section, 20% of width)

a contents section (middle right section, 80% of width)

On the left: The Vietnamese-German University logo (116 x 55 pixels)

In the center with <small> font

On the right: blank

Figure 2 Standard Header

4.1.4. Navigation Bar

Administrator Menu (see E.2 for an example)

User Menu (see E.8 for an example)

4.1.5. Contents Screen

4.2. Hardware Interfaces

4.3. Software Interfaces

4.4. Communications Interfaces

4.4.3. Web Browser

Appendix A: Glossary of Terms

Appendix B, Gantt Chart

Gantt chart Symbols

Deliverable Due Date

Project Status Symbols Planning/Progress Symbols

B Work Before Schedule Time

Software Requirements Specification 02/03/12

S Scheduled Activity Time

Prototype Web Site

X Scheduled But not Worked

X Scheduled But not Worked

Appendix C: Software Design Diagram

Terms and Conditions

1. Modify Personal Data

II. Review, Approve, Disapprove

Figure 3 Software Menu Module Overview

Appendix D: Database Elements