• Embed Doc
  • Readcast
  • Collections
  • CommentGo Back
Download
 
SoftCell SoftwareRequirementSpecification
Course 
CEN 3031 Software EngineeringDr. Robert M. Cubert, Professor
Prepared by 
Shintaro AgatsumaBojan BalticKristian DamkjerDonald Shea
 
Software Requirement Specification SoftCell Preface
Page 1
1. Preface
This section defines the audience for this document and the current revision. It is dividedinto two clauses. Clause 1 outlines the expected readers of this document. Clause 2details the version history of this document.
1.1 Expected Readership
The expected readership of this document is as follows:
 
Professors interested in using this software
 
Development team (SOFTCELL) and PA, SPA
 
Future support personnel that will assist the professors using this software.
1.2 Version History
Version 2.0 – November 1, 2000Updated the System Requirements Specification to reflect the current application.Version 1.1 – October 11, 2000Made a name correction for George. Changed name on title page to Bojan forconsistency with class roster.Version 1.0 – September 27, 2000We have finalized the document by adding the System Model, System Architecture,Glossary, and Index. We also made slight modifications to the Introduction and SoftwareRequirements sections. We removed the optional System Evolution section and theAppendix section since we have no appendices.Version 0.0 – September 20, 2000Being the first version of this document, there have been no changes yet. Since this is afirst draft changes are expected and a new SRS will be produced as changes are made.
 
Software Requirement Specification SoftCell Introduction
Page 2
2. Introduction
This section provides an introduction to our system. It is broken into three clauses.Clause 1 describes the need for this system. Clause 2 describes the functionality of thesystem. Clause 3 describes how the system fits into the strategic objectives of thecommissioning organization.
2.1 Necessity
This software system will be used to facilitate communication between the professor,students, and teaching assistants of a university course. It could also be used at otherlevels of education or even outside of the educational setting.
2.2 Functionality
The system will be a web-based application for a class web site that incorporates aprofessor interface, a student interface, and database of student. Below are brief descriptions of the four parts of the system.The professor interface will be PC based and will allow the professor to post such itemsas the class syllabus, contact information for the professor and all assistants, specialannouncements, and a record of all grades each student has received. The professor willbe able to easily make changes to each part.The student interface will allow each student to view the items posted by the professorand to access his/her grades.The database of student information will contain such items as student names, socialsecurity numbers, class and college, and e-mail addresses as well as identifyinginformation such as passwords and Social Security numbers, that will facilitate accesscontrol.
2.3 Purpose
This system is expected to help make the learning experience more productive thantraditional paper-based systems by enabling each student to easily access updated orchanged class information as well as by allowing two-way communication betweenstudents and instructors.
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...