and System Software Requirements Definition (SSRD)
The IGM On-Line Art Gallery
Team #6
Jay Shah Shreyas Nangalia Shivalika Goyal Anogh Paradkar Ramandeep Singh Anveshak Akula Godfrey Duke
Project Manager Operational Concept Engineer / Shaper(On-Campus) Feasibility Analyst System Architect Life Cycle Planner Requirements Engineer IIV&V / Shaper(Off-Campus)/ Requirements Engineer(OffCampus) IIV&V / QFP
Vyom Caesar
10/13/2008
System and Software Requirements Description (SSRD)
Version 1.1
Version History
Date
10/6/08
Author
Anveshak Akula
Version Changes made
1.0 Made original document Using Lean MBASE so no change The agreement numbers are changed.
Rationale
Initial requirement analysis document The original agreements were deleted while preparing the wikiwinwin report. So the agreements were created again.
10/13/08
Anveshak Akula
1.1
ba39318f180d4cf000e529e7e4f1113cfca7bff8.doc1
II
Version Date: 10/13/08
System and Software Requirements Description (SSRD)
Version 1.1
Table of Contents
System and Software Requirements Definition (SSRD)................................................I Version History..............................................................................................................II Table of Contents.........................................................................................................III Table of Tables.............................................................................................................IV
1.1.1. Introduction .....................................................................................................................................1 1.1.1.1. Purpose of SSRD............................................................................................................1 1.1.1.2. Status of SSRD...............................................................................................................1 1.1.2. Product Requirements......................................................................................................................2 1.1.2.1. Capability (Functional) Requirements............................................................................2 1.1.2.2. Level of Service (L.O.S.) Requirements .....................................................................3 1.1.3. Interface Requirements....................................................................................................................5 1.1.3.1. User Interface Standards Requirements ..................................5 1.1.3.2. Hardware Interface Requirements..................................................................................6 1.1.3.3. Communications Interface Requirements.......................................................................6 1.1.3.4. Other Software Interface Requirements.........................................................................6 1.1.4. Project Requirements.......................................................................................................................7 1.1.4.1. Tools Requirements........................................................................................................7 1.1.4.2. Language Requirements.................................................................................................7 1.1.4.3. Computer Hardware Requirements................................................................................7 1.1.4.4. Computer Software Requirements..................................................................................8 1.1.4.5. Computer Communication Requirements......................................................................8 1.1.4.6. Deployment Requirements.............................................................................................8 1.1.4.7. Transition Requirements.................................................................................................8 1.1.4.8. Support Environment Requirements ..............................................................................9 1.1.4.9. Budget and Schedule......................................................................................................9 1.1.5. Evolutionary Requirements...........................................................................................................10 1.1.5.1. Capability Requirements..............................................................................................10 1.1.5.2. Level of Service Requirement......................................................................................10 1.1.5.3. Software Interface Requirements.................................................................................10
ba39318f180d4cf000e529e7e4f1113cfca7bff8.doc1
III
Version Date: 10/13/08
System and Software Requirements Description (SSRD)
Version 1.1
Table of Tables
Table 1: Provide gallery for displaying images.............................................................2 Table 2: Provide functionality for uploading images, text, director and artist statement 2 Table 3: Provide facility to archive past exhibitions......................................................3 Table 4: System up time.................................................................................................3 Table 5: Query correctness.............................................................................................3 Table 6: System response time.......................................................................................4 Table 7: Interoperability.................................................................................................4 Table 8: Use USC color schemes...................................................................................5 Table 9: The GUI must match the sample GUI developed by the Infinite 9 development team..........................................................................................................5 Table 10: Use new IGM art gallery logo........................................................................5 Table 11: The GUI should be easy to use and attractive................................................6 Table 12: Interface with homepage developed by Infinite 9 team ............................6 Table 13: Follow Instructional-ICM guideline..............................................................7 Table 14: Use course required tools...............................................................................7 Table 15: Use PHP language..........................................................................................7 Table 16: Use SQL language.........................................................................................7 Table 17: Use Apache as a web-server..........................................................................8 Table 18: Use MySQL as a database.............................................................................8 Table 19: Deploy on Apache Web Server......................................................................8 Table 20: Provide training .............................................................................................8 Table 21: Test on Linux operating system ....................................................................9 Table 22: Cross browser testing.....................................................................................9 Table 23: Schedule of 24 weeks.....................................................................................9 Table 24: Provide online payment system.................................................................10 Table 25: Secure Payment............................................................................................10
ba39318f180d4cf000e529e7e4f1113cfca7bff8.doc1
IV
Version Date: 10/13/08
1.1.1.
Introduction
1.1.1.1. Purpose of SSRD
The purpose of the SSRD is to document the requirements of the project that derived from WinWin negotiation sessions. Moreover, the SSRD will act as a contract to all stakeholders about the delivered system. Hence, SSRD defines what the delivered system will do, what will be the behavior of the system and other project-specific stakeholders' agreed win conditions.
1.1.1.2. Status of SSRD
The current document is in Foundations Commitment Package. These requirements are based on the winwin negotiations which happened recently. The scope of the project has been reduced. The features which will be implemented in the Fall2008 semester are listed in the capability requirements sub-section of the Product requirement section. The features which might be implemented in the Spring2009 semester are listed in the capability requirements sub-section of the evolutionary requirements section.
1.1.2.
Product Requirements
1.1.2.1. Capability (Functional) Requirements
Table 1: Provide gallery for displaying images
Capability Requirement: Description: Priority: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post conditions(s): Win-Win Agreement(s):
CR-1: Provide gallery for displaying images. The users should be able to view the pictures of the artwork online through the IGM art gallery website. M (Must have) The images are retrieved from the database. Database Displaying the image on the screen GUI The images should be present in the database. The image is displayed on the screen Agreement43,4
Table 2: Provide functionality for uploading images, text, director and artist statement
Capability Requirement: Description: Priority: Input(s): Source(s): Output(s): Destination(s): Precondition(s): Post conditions(s): Win-Win Agreement(s):
CR-2: Provide functionality for uploading images. Functionality should be provided to the administrator to upload the images to the M database. (Must have) The path to the image on the administrator's system, data entered by the administrator and click on the upload button. Input from the administrator. A message saying data uploaded is displayed on the screen. The system database, GUI a. GUI screen for input b. The administrator should be logged in New time in or time out entry recorded to the database. GUI screen. Agreement2
Table 3: Provide facility to archive past exhibitions
Capability Requirement: CR-3: Provide facility to archive past exhibitions. Description: The past exhibitions should be sent to the archives and only the pictures from the current exhibition should be displayed on the gallery. Priority: M (Must have) Input(s): The images of past exhibitions from the database. Source(s): Database Output(s): A list of archives. Destination(s): GUI Precondition(s): a. The images should present in the database. Post conditions(s): List of archives on the GUI is also updated. Win-Win Agreement(s): Agreement44
1.1.2.2. Level of Service (L.O.S.) Requirements
Table 4: System up time
Level of Service Requirement: Description: Priority: Desired Level: Accepted Level: Measurable: Achievable: Relevant: Specific: Win-Win Agreement(s):
LOS-1: System up time The system uptime should be high. M (Must have) 100% of system service uptime excluding network and server downtime. 90% of system service uptime excluding network and server downtime. The time that the system is available to user Stable Internet, thorough testing All capability requirements All capability requirements Agreement41
Table 5: Query correctness
Level of Service Requirement: Description: Priority: Desired Level: Accepted Level: Measurable: Achievable: Relevant: Specific: Win-Win Agreement(s):
LOS-2: Query correctness The data that result from query operations should be correct. M (Must have) 100% correctness of data storage and retrieval 100% correctness of data storage and retrieval. The correctness of query result SQL queries are to be tested and checked before implementation. CR-1, CR-2 CR-1, CR-2 Agreement40
Table 6: System response time
Level of Service Requirement: Description: Priority: Desired Level: Accepted Level: Measurable: Achievable: Relevant: Specific: Win-Win Agreement(s):
LOS-3: System response time The time it takes to get a result when a specific functionality is invoked by a user must be low. S (Should have) 1 second 2 second; not depend on network speed when tested independently System response time when user invokes different functions of the system and the time the system takes for page advancing. The time it takes to get a result when a specific functionality. All capability requirements All capability requirements Agreement9
Table 7: Interoperability
Level of Service Requirement: Description: Priority: Desired Level Accepted Level Measurable Achievable Relevant: Specific Win-Win Agreement(s):
LOS-4: Interoperability The system should interface properly with the main website being developed by the Infinite 9 team. M (Must have) Compatible with all modules being developed by the infinite 9 team. Compatible with all modules being developed by the infinite 9 team. Number of modules that can be integrated with the system Proper coordination between the two teams. The system should be designed and implemented such that it is compatible with the product being developed by Infinite 9 team. All the modules of the system. All the modules of the system. Agreement10
1.1.3.
Interface Requirements
Table 8: Use USC color schemes
1.1.3.1. User Interface Standards Requirements
System Interface Requirement: Description: Priority: Win-Win Agreement(s): SR-1: Use USC color scheme in the GUI. It is required by the client that the GUI must conform with the USC color scheme M (Must have) Agreement5
Table 9: The GUI must match the sample GUI developed by the Infinite 9 development team
System Interface Requirement: Description: Priority: Win-Win Agreement(s):
SR-2: The GUI must match the sample GUI developed by the Infinite 9 development team. It is required by the client that the GUI must match the sample GUI developed by the Infinite 9 development team. M (Must have) Agreement5
Table 10: Use new IGM art gallery logo
System Interface Requirement: Description: Priority: Win-Win Agreement(s):
SR-3: Use new IGM art gallery logo It is required by the client that the new IGM art gallery logo be used in the GUI. M (Must have) Agreement5
Table 11: The GUI should be easy to use and attractive
System Interface Requirement: Description: Priority: Win-Win Agreement(s):
SR-4: The GUI should be easy to use and attractive It is required by the client that the GUI be easy to use and attractive. M (Must have) Agreement5
1.1.3.2. Hardware Interface Requirements
There is no hardware Interface requirement.
1.1.3.3. Communications Interface Requirements
There is no communication Interface Requirement.
1.1.3.4. Other Software Interface Requirements
Table 12: Interface with homepage developed by Infinite 9 team
System Interface Requirement: Description: Priority: Win-Win Agreement(s):
SR-5: Interface with homepage developed by Infinite 9 team The product must interface well with the homepage developed by the infinite 9 team M (Could have) Aggreement18
1.1.4.
Project Requirements
1.1.4.1. Tools Requirements
Table 13: Follow Instructional-ICM guideline
Project Requirement: Description: Priority: Win-Win Agreement(s):
PR-1: Follow Instructional-ICM guideline The project processes and deliverables must follow the Instructional-ICM guideline. M (Must have) Aggreement19
Table 14: Use course required tools
Project Requirement: Description: Priority: Win-Win Agreement(s):
PR-2: Use course required tools It is required by CS577 course to use the following tools: MS Project, WikiWinWin, Effort Reporting system, DART, Rationale Soft...