KFUPM VIPER Team
Supply Chain Management System For Ejada Company SRS
VIPER TEAM (Team#6) Name Abdulrahm Abdulrahman an Al-Thuba Al-Thubaiti iti Anas Al-Hasani Al-Hasani Faisal Al-Ghamdi Mohammed Al-Mathami Nasser Al-Al-Khaldi Abdullah Abdullah Al-Jallal Al-Jallal
Stu ID#
245406 245050 237263 245040 226286 231945
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
Revision History Date 26/Nov/2008
Version 0.1
Description - Initializing the SRS Document -writing the introduction
Author Abdulrahman Al Thubaiti Thubaiti
29/Nov/2008
1.0
-complete SRS Document.
VIPER team members
20/Dec/2008
1.1
1- In the UCs discretion the precondition and the first step in the UC discretion are not the same as well as the some of Branching Action need to be changed as it is explained in the meeting.
Mohammad AlMathami Faisal Al-Ghamdi
2- Adding the logical DB section which is the tables that we have in our system. 3- Adding UC diagram into the appendix section as a last thing in the report. 20/Dec/2008
1.2
1- Modifying and adding in Communication Communication interface.
Anas Al-Hasani
2- Modify and improve format document. 20/Dec/2008
Confidential
2.0
1. Adding Change Management Process 2. Finalizing the SRS and release v2.0
Team#6 , 2008
Abdulrahman Abdulrahman Al-Thubaiti Al-Thubaiti
Page 2
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
Revision History Date 26/Nov/2008
Version 0.1
Description - Initializing the SRS Document -writing the introduction
Author Abdulrahman Al Thubaiti Thubaiti
29/Nov/2008
1.0
-complete SRS Document.
VIPER team members
20/Dec/2008
1.1
1- In the UCs discretion the precondition and the first step in the UC discretion are not the same as well as the some of Branching Action need to be changed as it is explained in the meeting.
Mohammad AlMathami Faisal Al-Ghamdi
2- Adding the logical DB section which is the tables that we have in our system. 3- Adding UC diagram into the appendix section as a last thing in the report. 20/Dec/2008
1.2
1- Modifying and adding in Communication Communication interface.
Anas Al-Hasani
2- Modify and improve format document. 20/Dec/2008
Confidential
2.0
1. Adding Change Management Process 2. Finalizing the SRS and release v2.0
Team#6 , 2008
Abdulrahman Abdulrahman Al-Thubaiti Al-Thubaiti
Page 2
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
Table of Contents 1. Introduction……………………………………………………………………….…4 1.1 Purpose ……………………………………………………………….……..4 1.2 Scope………………………………………………………………….……..4 1.3 Definitions, Acronyms and Abbreviations ……………………………….…4 1.4 References …………………………………………………………………..5 1.5 Overview ……………………………………………………………………5 2. Overall Description…………………………………………………………….……5 2.1 Product Perspective………………………………………………………….7 2.2 Product Functions …………………………………………………………...8 2.3 User Characteristics …………………………………………………………8 2.4 Constraints ……………………………………………………………….….8 2.5 Assumptions & Dependencies ………………………………………………8 2.6 Apportioning of Requirements………………………………………………8 3. Specific Requirements ……………………………………………………………...8 3.1 Interface Requirements ……………………………………………….……..8 3.1.1 User Interfaces …………………………………………………………..9 3.1.2 Hardware Interfaces ………………………………………………..…..28 3.1.3 Software Interfaces …………………………………………………..…28 3.1.4 Communication Interfaces …………………………………………...…28 3.2 Functional Requirements ………………………………………………...…29 3.3 Performance Requirements …………………………………………...……85 3.4 Logical Database Requirements…………………………………………….85 3.5 Design Constraints……………………………………………………...…..85 3.6 Software System Attributes…………………………………………………85 3.6.1 Reliability……………………………………………………………….85 3.6.2 Availability ……………………………………………………………..85 3.6.3 Security …………………………………………………………………86 3.6.4 Maintainability…………………………………………………………..86 3.6.5 Portability ……………………………………………………………….86 4. Change Management Process……………………………………. ………………….86 Appendix……………………………………………………………………………….87 Use Case Diagrams………………..…………………………………………………….87
Confidential
Team#6 , 2008
Page 3
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
Software Requirements Specification 1.
Introduction
1.1
Purpose
The purpose of this document is to fully describe the external behavior of the SCM system in terms of functional requirements. It also describes the nonfunctional requirements such as usability, availability, security, maintainability and reliability. In addition, it specifies the design constraints and standards that are needed to be applied on SCM. 1.2
Scope
This document represents specification of the SCM system requirements. It serves as the baseline document on which the subsequent software development life cycle phases are built. 1.3 1.3
Defi Defini niti tion ons, s, Acro Acrony nyms ms and and A Abb bbre revi viat atio ions ns
1.4
Term
Description
SYSTEM
Supply Ch Chain Ma Management So Software.
KFUPM
King Fahad University of Petroleum and Minerals
SCM
Supply Chain Management
STD
State Transition Diagram
SRS
Software Requirements Specification
ERP
Enterprise Resource Planning
References
The references of this document are:
1.5
SCM Software Requirements Specification document v.1.2.
Use Case & STD Documentation v1.5
SCM Conceptual Class Model and Sequence Diagram document v.2.0
SCM Screen layouts document v.1.2.
SWE 417-SRS Template-USE
Overview
This SRS document is organized as flows:
Overall description of SCM which include product perspective, product functions, SCM’s user characteristics, constraints, assumptions & dependencies and apportioning of requirements.
Specific Requirements which include , interface requirements, functional requirements, performance requirements, logical database requirements, design Confidential
Team#6 , 2008
Page 4
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
constraints and software system attributes.
Change management process.
2. Overall Description
2.1 Product Perspective: The perspective of product conduct in delivering Ejada company products like IT products, Business Consultation and other IT service in fast way and less cost than other alternative way. There are other well known SCM systems from Oracle and SAP, they are used in big companies and connecting with other systems but with the same main functionality that is provided by our SCM. Our system scope is limited by Ejada and there requests.
2.2 Product Functions
Ejada SCM will: Provide a simple Customer service management process Determine mutually satisfying goals between organization and customers Establish and maintain customer rapport
Confidential
Team#6 , 2008
Page 5
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
Produce positive feelings in the organization and the customers Maintain Procurement process Manage Product development and commercialization Coordinate with customer relationship management to identify customer-articulated needs select materials and suppliers in conjunction with procurement Develop production technology in manufacturing flow to manufacture and integrate into the best supply chain flow for the product/market combination. Maintain Manufacturing flow management process Manage Physical distribution Maintain Outsourcing and Partnerships Maintain Measurement Performance Maintain Cost Performance Maintain Customer Service Performance Maintain Productivity measures Performance Maintain Asset measurement Performance Maintain Quality Performance
Confidential
Team#6 , 2008
Page 6
Supply Chain Management System Software Requirements Specification
Confidential
Version: 1.1 Date: 20/12/2008
Team#6 , 2008
Page 7
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
2.3 User Characteristics
The users are Ejada’s employees, customers and suppliers. It considers that they have the high school level or higher and they can read and write in English with basic knowledge of using computer programs. 2.4 Constraints
The system has many constraints. For example, the system must be web-based and all tools must be compliant with .Net technologies, i.e., We must use ASP.NET and C# as programming language and MS SQL as DBMS. We are also constrained with Ejada's framework and the system will later be integrated with other two modules in the framework. Ejada has some programming standards that we must commit to. 2.5 Assumptions & Dependencies
We assume that the server machine of the system has a suitable Microsoft OS. This machine has a connection to internet. 2.6 Apportioning of Requirements
Our SCM system requires including all requirements prior to the first delivery. 3. Specific Requirements 3.1 Interface Requirements 3.1.1 User Interfaces The system is a web base system so, it will interact with its users with web components interface. The users move through pages containing activities or direction to some other activities. The system interface will looks like following:
•
intro page to the system. Direct link to login page.
Confidential
Team#6 , 2008
Page 8
Supply Chain Management System Software Requirements Specification
• • • •
•
Version: 1.1 Date: 20/12/2008
Log in page contain 2 text fields and 1 list box : username, password and domain. The user should write his/her username, password and select in which domain he/she is. Domain list box has 3 choices [ coordinator, costumer and supplier ]. After the user click send or hit enter button the system will direct the user to its domain if he/she is in coordinator, costumer or supplier section. If username or password is wrong the system will direct the user to an error page.
Confidential
Team#6 , 2008
Page 9
Supply Chain Management System Software Requirements Specification
• •
Version: 1.1 Date: 20/12/2008
if the information provided by the user is wrong this page will appear to him/her. User can click on [ Try again ] link, so he/she can try to log in again.
Coordinator section:
• • •
First page in the coordinator domain. User can select customer, supplier, requests or items management section. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 10
Supply Chain Management System Software Requirements Specification
• • • • • • •
Version: 1.1 Date: 20/12/2008
Customer management section in coordinator domain. This page display the last 5 new customer. User can click on [ view detail ] for more information about a customer. User can click on [ view all customers ] link, he/she will directed to page will full customer list. User can click on [ add new customer ] link, to add a new customer to the system. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 11
Supply Chain Management System Software Requirements Specification
• •
• •
Version: 1.1 Date: 20/12/2008
add customer page contain 4 information fields. After writing all the information, user will click on [ add ] button to add the customer to the system. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 12
Supply Chain Management System Software Requirements Specification
•
• • •
Version: 1.1 Date: 20/12/2008
when click on [ view detail ] of some customer. The system will direct the user to view customer details. Two link appear above the box, edit and delete link. This will perform on the current page. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 13
Supply Chain Management System Software Requirements Specification
•
Version: 1.1 Date: 20/12/2008
page to conform the deletion. User must click on either yes or no.
Confidential
Team#6 , 2008
Page 14
Supply Chain Management System Software Requirements Specification
• •
• •
Version: 1.1 Date: 20/12/2008
edit customer page contain 4 information fields. After editing all the information, user will click on [ edit ] button to edit the customer information. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 15
Supply Chain Management System Software Requirements Specification
• • • • • • •
Version: 1.1 Date: 20/12/2008
Items management section in coordinator domain. This page display the last 5 new Items. User can click on [ view detail ] for more information about item. User can click on [ view all Items ] link, he/she will directed to page will full items list. User can click on [ add new Items ] link, to add a new item to the system. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 16
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
when click on [ view detail ] of item. The system will direct the user to view item details. Two link appear above the box, edit and delete link. This will perform on the current page. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 17
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
edit item page contain 2 information fields. After editing all the information, user will click on [ save ] button to edit the item information. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 18
Supply Chain Management System Software Requirements Specification
• • • • • • •
Version: 1.1 Date: 20/12/2008
Supplier management section in coordinator domain. This page display the last 5 new supplier. User can click on [ view detail ] for more information about a supplier. User can click on [ view all supplier ] link, he/she will directed to page will full supplier list. User can click on [ add new supplier ] link, to add a new supplier to the system. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 19
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
when click on [ view detail ] of supplier. The system will direct the user to view supplier details. Two link appear above the box, edit and delete link. This will perform on the current page. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 20
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
edit supplier page contain 4 information fields. After editing all the information, user will click on [ edit ] button to edit the supplier information. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 21
Supply Chain Management System Software Requirements Specification
• • • • • • •
Version: 1.1 Date: 20/12/2008
Requests management section in coordinator domain. This page display the last 5 new customer requests and the last 5 requests to suppliers. User can click on [ view detail ] for more information about a requests. User can click on [ view all Requests ] link, he/she will directed to page will full customer list. User can click on [ add new Requests ] link, to add a new requests to the system. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 22
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
when click on [ view detail ] of request. The system will direct the user to view request details. Two link appear above the box, edit and delete link. This will perform on the current page. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 23
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
edit request page contain 2 information fields. After editing all the information, user will click on [ save ] button to edit the request information. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Customer section:
Confidential
Team#6 , 2008
Page 24
Supply Chain Management System Software Requirements Specification
• • • • • • • •
Version: 1.1 Date: 20/12/2008
The main page in customer domain. This page display the last 5 new requests. User can click on [ view detail ] for more information about request. User can click on [ view all requests ] link, he/she will directed to page will full requests list. User can click on [ add new request ] link, to add a new requests to the system. User can edit his/her profile, a link [ edit profile ] there to do so. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 25
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
add request page contain 2 information fields. After writing all the information, user will click on [ send ] button to add the request information. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 26
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
when click on [ view detail ] of request. The system will direct the user to view request details. Two link appear above the box, edit and delete link. This will perform on the current page. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 27
Supply Chain Management System Software Requirements Specification
• • • •
Version: 1.1 Date: 20/12/2008
edit request page contain 2 information fields. After editing all the information, user will click on [ save ] button to edit the request information. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 28
Supply Chain Management System Software Requirements Specification
• •
• •
Version: 1.1 Date: 20/12/2008
edit customer profile contain 4 information fields. After editing all the information, user will click on [ save ] button to edit the customer profile information. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 29
Supply Chain Management System Software Requirements Specification
• • • •
• • •
Version: 1.1 Date: 20/12/2008
Supplier section:
The main page in supplier domain. This page display the last 5 new requests. User can click on [ view detail ] for more information about request. User can click on [ view all supply requests ] link, he/she will directed to page will full requests list. User can edit his/her profile, a link [ edit profile ] there to do so. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 30
Supply Chain Management System Software Requirements Specification
• • • • •
Version: 1.1 Date: 20/12/2008
when click on [ view detail ] of request. The system will direct the user to view request details. Two link appear above the box, edit and delete link. This will perform on the current page. The page contain a feedback box, the supplier may send his feedback about the request. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 31
Supply Chain Management System Software Requirements Specification
•
Version: 1.1 Date: 20/12/2008
Redirected page after sending the feedback.
Confidential
Team#6 , 2008
Page 32
Supply Chain Management System Software Requirements Specification
• •
• •
Version: 1.1 Date: 20/12/2008
edit supplier profile contain 4 information fields. After editing all the information, user will click on [ save ] button to edit the supplier profile information. Navigation bar under the banner of the system that allow user to navigate through pages. User can click on [ Logout ] link, so that he/she logged out f rom the system.
Confidential
Team#6 , 2008
Page 33
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.1.2 Hardware Interfaces
The system has no hardware interface requirements. 3.1.3 Software Interfaces
Name Mnemonic Specification Number Version Number Source Purpose of Interfacing
SQL- Server SQL-DB
Name Mnemonic Specification Number Version Number Source Purpose of Interfacing
Internet Explorer IE
Name Mnemonic Specification Number Version Number Source Purpose of Interfacing
Mozilla firefox Firefox
Version 7.0.1 http://www.microsoft.com/sqlserver/2008/en/us/default.aspx The system must use SQL server as its database.
Version 6 and Version 7 http://www.microsoft.com/windows/products/winfamily/ie/default.mspx The user should use this browser, so that he can display the system and work on it.
Version 2 and Version 3 http://www.mozilla.com/en-US/firefox/ The user should use this browser, so that he can display the system and work on it.
3.1.4 Communication Interfaces
The SCM system will use TCP/IP as the main communication protocol trough internet/network. Also, it might communicate with external systems in the f uture, such as customer relation management system and HR systems. The scope of our system does not require to interact with other interfaces but it can be customized.
Confidential
Team#6 , 2008
Page 34
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2 Functional Requirements 3.2.1.1 Manage Requests USE CASE # 1 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS
Manage Requests The main requests management page that coordinator will manage all request from customer or to suppliers Company, Summary -Must the coordinator login - The coordinator can manage his request can add ,view or edit his requests - Login in failed - There is No suppliers for his requests Coordinator , Supplier, Customer
Step 1 2 3 Step
Action The coordinator press “Manage Requests” The coordinator use any function. The coordinator will manage all requests function. Branching Action - "Error!" message. Branching Action
1
Coordinator may use phone to request from suppliers
SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Confidential
Manage Requests Top
What is the coordinator cannot manage requests? What is the coordinator cannot use requests functions? Release 1.0
Login Add Request , View Requests
Team#6 , 2008
Page 35
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.2.1 Add Request USE CASE #2 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Add Request Coordinator can add new request and send it to his supplier Company , Summary -Must the coordinator login - The coordinator can add new request. - The request sent to supplier - Login in failed - There is No suppliers for his requests or send error Coordinator , Supplier
When the coordinator needs to add new request. Step Action 1 The coordinator press “Add Request” 2 The coordinator fills the request form. 3 The coordinator will send the request to supplier Step Branching Action 1a - "Error!" message Branching Action 1
Coordinator may use phone to request from suppliers
RELATED Add Request INFORMATION Priority: Top 10 minutes for request, 2 days until accept Performance Frequency 10/day Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot add new requests? Due Date Release 1.0 ...any other management information... Requests Management Superordinates Subordinates None
Confidential
Team#6 , 2008
Page 36
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.2.2 Sequence Diagram sd Add Request s
Coordinator
Request
Add Requ est()
Request Form()
Fill Form()
Request Created()
3.2.3.1 View Requests USE CASE #3 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
View Requests Coordinator issues requests , coordinator can show all requests that sent his supplier or that came from his customer Company , Summary -Must the coordinator login - The coordinator can show all requests. - Login in failed - The coordinator cannot view all requests. Coordinator , Supplier, Customer
When the coordinator needs to view requests. Step Action 1 The coordinator press “View Requests” 2 The coordinator view list of requests. Step Branching Action 1a "Error!" message Branching Action 1 2
Confidential
Coordinator may want to see the customers requests only Coordinator may want to see the requests that sent to suppliers
Team#6 , 2008
Page 37
Supply Chain Management System Software Requirements Specification
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
View Requests Top 10 seconds to show the list 10/day not yet determined What is the coordinator cannot view requests? Release 1.0
Manage Requests View Request Details
3.2.3.2 Sequence Diagram sd CoordViewSuppliers
Coordinator
R Request
view requests()
li st o f reque sts is returned()
3.2.4.1 View Request Details USE CASE #4 View Request Details Coordinator can show the details of any request that he chose. Goal in Context Scope & Level Company , Summary -Must the coordinator login Preconditions - The coordinator can show the details of a request. Success End Condition Failed End - The coordinator cannot show the details of a request. Condition Primary, Coordinator , Supplier, Customer Secondary Actors Trigger When the coordinator need to view the details of a request. DESCRIPTION Step Action 1 The coordinator press “View Request Details” 2 The coordinator views the details of a request. EXTENSIONS Step Branching Action 1a "Error!" message Confidential
Team#6 , 2008
Page 38
Supply Chain Management System Software Requirements Specification
SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
Branching Action
View Request Details
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Middle 10 seconds to show the details of a request. 10/day not yet determined What is the coordinator cannot view the details of a request? Release 1.0
View Requests Delete Request, Edit Request
3.2.1.2 Sequence Diagram sd View Request details s
Coordinator
Request
View Request details()
Request report created()
3.2.5.1 Edit Request USE CASE # 5 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Confidential
Edit Request The Coordinator can edit request and notify his supplier Company , Summary -Must the coordinator login - The coordinator can edit exist request. - The notification will send to supplier. - Login in failed - The coordinator cannot edit exist request. - The notification cannot send to supplier. Coordinator , Suppliers
Team#6 , 2008
Page 39
Supply Chain Management System Software Requirements Specification
Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
When the coordinator needs to edit any exist request. Step Action 1 The coordinator press “Edit Request” 2 The coordinator modifies the request information. 3 The coordinator will send a notification to supplier Step Branching Action 1a "Error!" message Branching Action 1
Coordinator may use phone to request from suppliers
Edit Request RELATED INFORMATION Top Priority: Performance 10 minutes for edit, on time change 10/day Frequency Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot edit any request? Release 1.0 Due Date ...any other management information... View Request Details Superordinates Subordinates None 3.2.5.2 Sequence Diagram sd Edit Request s
Coordinator
Request
Edit Request ()
Request Form()
Update Reque st form() Request updated()
Confidential
Team#6 , 2008
Page 40
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.6.1 Delete Request USE CASE #6 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Delete Request The Coordinator can delete request and notify his supplier Company , Summary -Must the coordinator login - The coordinator can delete exist request. - The notification will send to supplier. - Login in failed - The coordinator cannot delete exist request. - The notification cannot send to supplier. Coordinator , Suppliers
When the coordinator needs to delete any exist request. Step Action 1 The coordinator press “Delete Request” 2 The information about the request will show. 3 Press “Delete” to processing the deleting 4 The coordinator will send a notification to supplier Step Branching Action 1a "Error!" message Branching Action 1
Coordinator may use phone to delete the request from suppliers
RELATED Delete Request INFORMATION Priority: 1 minute for delete Performance Frequency 10/day Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot delete requests? Due Date Release 1.0 ...any other management information... View Request Details Superordinates Subordinates None
Confidential
Team#6 , 2008
Page 41
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.6.2 Sequence Diagram sd Delete Request s
Coordinator
Request
Delete Request()
Request removed()
3.2.7.1 Manage Items
USE CASE # 7 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS
Manage Items The main items management page that coordinator will manage the items that he have and may supply to customer Company, Summary -Must the coordinator login - The coordinator can manage his items can add ,view or edit his items - Login in failed - There is No items to manage or supply it Coordinator , Supplier, Customer
Step 1 2 3 Step 1a
Action The coordinator press “Manage Items” The coordinator use any function. The coordinator will manage all items function. Branching Action - "Error!" message Branching Action
1
Coordinator may use some different items
SUBVARIATIONS
RELATED INFORMATION Confidential
Manage Items
Team#6 , 2008
Page 42
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
Top Priority: Performance 5 second to show items functions Frequency Channels to actors Not yet determine OPEN ISSUES What is the coordinator cannot manage items? What is the coordinator cannot use items functions? Due Date Release 1.0 ...any other management information... Login Superordinates Subordinates Add Item , View Items
3.2.8.1 Add Item USE CASE# 8 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management Confidential
Add Item Coordinator can add new items and may supply it to our customer Company , Summary -Must the coordinator login - The coordinator can add new item -
The coordinator cannot add new item
Coordinator , Supplier ,Customer
When the coordinator needs to add new item. Step Action 1 The coordinator press “Add Item” 2 The coordinator fills the item form. 3 The coordinator will save the item. Step Branching Action 1a "Error!" message Branching Action
Add Item Top 10 minutes for add item 10/day not yet determined What is the coordinator cannot add new items? Release 1.0
Team#6 , 2008
Page 43
Supply Chain Management System Software Requirements Specification
information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
Manage Items None
3.2.8.2 Sequence Diagram sd Add Item s
Coordinator
It em
Add Item ()
Item Form()
Fill form()
Item created()
3.2.9.1 View Items USE CASE # 9 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
View Items The coordinator can view all items that he have ,that may receive from supplier and may supply it f or his customers Company , Summary -Must the coordinator login - The coordinator can view all Items. - Login in failed - The coordinator cannot view all Items. Coordinator , Supplier, Customer
When the coordinator needs to view all I tems. Step Action 1 The coordinator press “View Items” 2 The coordinator view list of Items Step Branching Action 1a "Error!" message Branching Action 1 2
Confidential
Coordinator may want to see the Items category Coordinator may want to see the Items that sent to customers Team#6 , 2008
Page 44
Supply Chain Management System Software Requirements Specification
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
View Items Top 10 seconds to show the list 10/day not yet determined What is the coordinator cannot view items? Release 1.0
Manage Items View Item Details
3.2.9.2 Sequence Diagram sd CoordViewItems s
Coordinator
It em
view items()
list of items is returned()
3.2.10.1 View Item Details USE CASE # 10 View Item Details Coordinator can show the details of any items that he chooses. Goal in Context Scope & Level Company , Summary -Must the coordinator login Preconditions - The coordinator can show the details of an item. Success End Condition Failed End - The coordinator cannot show the details of an item. Condition Primary, Coordinator , Supplier, Customer Secondary Actors Trigger When the coordinator need to view the details of an item. DESCRIPTION Step Action 1 The coordinator press “View Item Details” 2 The coordinator views the details of an item. EXTENSIONS Step Branching Action 1a "Error!" message Confidential
Team#6 , 2008
Page 45
Supply Chain Management System Software Requirements Specification
SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
Branching Action
View Item Details middle 10 seconds to show the details of an item. 10/day not yet determined What is the coordinator cannot view the details of a n item? Release 1.0
View Items Delete Item, Edit Item
3.2.10.2 Sequence Diagram sd View Item details s
Coordinator
It em
View Item detail s()
Item report created()
3.2.11.1 Edit Item USE CASE # 11 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger Confidential
Edit Item. The Coordinator can edit item that he want. Company , Summary -Must the coordinator login - The coordinator can edit exist item. - The notification will send to supplier and customer if need. - Login in failed - The coordinator cannot edit exist item. Coordinator , Supplier, Customer
When the coordinator needs to edit any exist item. Team#6 , 2008
Page 46
Supply Chain Management System Software Requirements Specification
DESCRIPTION
Step 1 2 3
EXTENSIONS
Step 1a
SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
Action The coordinator press “Edit Item” The coordinator modifies the item information. The coordinator will send a notification to supplier or customer if need. Branching Action "Error!" message Branching Action
RELATED Edit Item INFORMATION Priority: Top Performance 10 minutes for edit, on time change Frequency 10/day Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot edit any request? Release 1.0 Due Date ...any other management information... Superordinates View Items Details Subordinates None 3.2.11.2 Sequence Diagram sd Edit Item s
Coordinator
It em
Edit Item()
Item form ()
Update Item form() Item updated()
3.2.12.1 Delete Item USE CASE # 12 Goal in Context Scope & Level Confidential
Delete Item The Coordinator can delete any item from his list and his supply. Company , Summary Team#6 , 2008
Page 47
Supply Chain Management System Software Requirements Specification
Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
-Must the coordinator login - The coordinator can delete exist item. - Login in failed - The coordinator cannot delete exist item. Coordinator.
When the coordinator needs to delete any exist item. Step Action 1 The coordinator press “Delete Item” 2 The information about the item will show. 3 Press “Delete” to processing the deleting Step Branching Action 1a "Error!" message Branching Action
Delete Item RELATED INFORMATION Priority: Performance 1 minute for delete Frequency 10/day Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot delete an item? Release 1.0 Due Date ...any other management information... Superordinates View Item Details Subordinates None
3.2.12.2 Sequence Diagram sd Delete Item s
Coordinator
It em
Delete Item() Item removed()
Confidential
Team#6 , 2008
Page 48
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.13.1 Manage Resources Locations USE CASE # 13 Goal in Context
Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS
Manage Resources Locations The main resources locations management page that coordinator will manage the resources locations that he have and may use it to store or supplying. Company, Summary -Must the coordinator login - The coordinator can manage his resources locations can add, view or edit his resources locations. - Login in failed - There is No resources locations to manage or supply from it Coordinator
Step 1 2 3 Step 1a
SUBVARIATIONS
1
Action The coordinator press “Manage Resources Locations” The coordinator use any function. The coordinator will manage all resources locations function. Branching Action - "Error!" message Branching Action
Coordinator may use some different locations
Manage Resources Locations RELATED INFORMATION Top Priority: Performance 5 second to show resources locations functions Frequency Channels to actors Not yet determine OPEN ISSUES What is the coordinator cannot manage resources locations? What is the coordinator cannot use resources locations functions? Due Date Release 1.0 ...any other management information... Superordinates Login Subordinates Add Location , View Locations
Confidential
Team#6 , 2008
Page 49
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.14.1 Add Location USE CASE # 14 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Add Location Coordinator can add new resources locations and may start to use it in our supply and storing. Company , Summary -Must the coordinator login. - The coordinator can add new resource location. -
The coordinator cannot add new resource location.
Coordinator
When the coordinator needs to add new resource location. Step Action 1 The coordinator press “Add Location” 2 The coordinator fills the location form. 3 The coordinator will save the location. Step Branching Action 1a "Error!" message Branching Action May add nearest resources locations.
Add Location RELATED INFORMATION Priority: Top Performance 10 minutes for add location 10/day Frequency Channels to actors not yet determined What is the coordinator cannot add new locations? OPEN ISSUES Release 1.0 Due Date ...any other management information... Superordinates Manage Resources Locations None Subordinates
3.2.14.2 Sequence Diagram
Confidential
Team#6 , 2008
Page 50
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
sd Add Location s
Coordinator
Resource Location
Add Loca ti on()
Location Form()
Fill fo rm()
Resource Location created()
3.2.15.1 View Locations USE CASE # 15 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
View Locations The coordinator can view all resources locations that he have, that use to supplying our customer and store our items. Company , Summary -Must the coordinator login - The coordinator can view all resources locations. - Login in failed - The coordinator cannot view all resources locations. Coordinator
When the coordinator needs to view all locations. Step Action 1 The coordinator press “View Locations”. 2 The coordinator view list of Locations. Step Branching Action 1a "Error!" message Branching Action 1 2
RELATED INFORMATION Priority: Performance Confidential
Coordinator may want to see the Locations category Coordinator may want to see the Locations that nearest to our customer.
View Locations Top 10 seconds to show the list Team#6 , 2008
Page 51
Supply Chain Management System Software Requirements Specification
Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
10/day not yet determined What is the coordinator cannot view locations? Release 1.0
Manage Resources Locations View Locations Details
3.2.15.2 Sequence Diagram sd CoordView Locations
Coordinator
Resource L Locations view locations()
li st of resource lo actio ns is returned()
3.2.16.1 View Location Details View Location Details USE CASE # 16 Goal in Context Coordinator can show the details of resource location that he chooses. Scope & Level Company , Summary -Must the coordinator login. Preconditions Success End - The coordinator can show the details of a location. Condition Failed End - The coordinator cannot show the details of a location. Condition Coordinator Primary, Secondary Actors Trigger When the coordinator need to view the details of a location. DESCRIPTION Step Action 1 The coordinator press “View Location Details” 2 The coordinator views the details of a location. EXTENSIONS Step Branching Action 1a "Error!" message SUBBranching Action VARIATIONS
Confidential
Team#6 , 2008
Page 52
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
View Location Details
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
middle 10 seconds to show the details of a location. 10/day not yet determined What is the coordinator cannot view the details of a location? Release 1.0
View Locations Delete Locations, Edit Location
3.2.16.2 Sequence Diagram sd View Location details s
Coordinator
Resource Location
View Location details()
Location report created()
3.2.17.1 Edit Location USE CASE # 17 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS
Confidential
Edit Location. The Coordinator can edit a location that he wants. Company , Summary -Must the coordinator login -The coordinator press “Edit Location” - The coordinator can edit exist location. - Login in failed - The coordinator cannot edit exist location. Coordinator
When the coordinator needs to edit any exist location. Step Action 1 The coordinator press “Edit Location” 2 The coordinator modifies the location information. Step Branching Action 1a "Error!" message Team#6 , 2008
Page 53
Supply Chain Management System Software Requirements Specification
SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
Branching Action
RELATED Edit Location INFORMATION Priority: Top 10 minutes for edit, on time change Performance Frequency 10/day Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot edit any location? Due Date Release 1.0 ...any other management information... View Locations Details Superordinates Subordinates None 3.2.17.2 Sequence Diagram sd Edit Location s
Coordinator
Resource Location
Edit Location() Location form ()
Update Location form()
Location updated()
3.2.18.1 Delete Location USE CASE # 18 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Confidential
Delete Location The Coordinator can delete any location from his list. Company , Summary -Must the coordinator login - The coordinator can delete exist location. - Login in failed - The coordinator cannot delete exist location. Coordinator. Team#6 , 2008
Page 54
Supply Chain Management System Software Requirements Specification
Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
When the coordinator needs to delete any exist location. Step Action 1 The coordinator press “Delete Location” 2 The information about the location will show. 3 Press “Delete” to processing the deleting Step Branching Action 1a "Error!" message Branching Action
RELATED Delete Location INFORMATION Priority: 1 minute for delete Performance Frequency 10/day Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot delete a location? Due Date Release 1.0 ...any other management information... View Location Details Superordinates Subordinates None 3.2.18.2 Sequence Diagram sd Delete Location s
Coordinator
Resource Location
Delete Location()
Location removed()
3.2.19.1 Edit Profile USE CASE # 19 Confidential
Edit Profile Team#6 , 2008
Page 55
Supply Chain Management System Software Requirements Specification
Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS
SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
The supplier can edit his profile. The profile contains the name of the supplier, the address, contact person and e-mail… etc. Primary Task - The actor has logged in. The supplier profile is updated to the newly entered values. The older profile remains as is. An error message is generated. Primary: Supplier Secondary: Coordinator (by use case Edit Supplier) Clicking on the proper link for editing the profile. Step Action 1 He clicks on the proper link to edit his profile. 2 Whether he make changes or not, when he clicks on the proper link to submit the profile values, the current values of the profile is saved and he is returned to the main menu. Step Branching Action 1a Invalid input : Generating error message and discard changes. Branching Action none
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Confidential
Edit Profile Critical (some functions depend on successfulness of this UC) Must not exceed 1 sec to save the new input values. Once every 2-3 months. Database.
Team#6 , 2008
Page 56
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.19.2 Sequence Diagram
3.2.20.1 View Supply Requests USE CASE # 20 View Supply Requests To show a list of pending requests. Goal in Context Scope & Level Primary Task Preconditions - The actor has logged in. Success End The list of pending requests is rendered. Condition Failed End An error message is generated. Condition Primary, Primary: Supplier Secondary Actors Trigger Clicking on the proper link for viewing the supply requests. DESCRIPTION Step Action
EXTENSIONS
SUBVARIATIONS
Confidential
1 2 Step 1a
He clicks on the proper link to view supply requests. A list of pending requests is listed. Branching Action If there is no requests : A message is displayed stating that there is no requests. Branching Action
Team#6 , 2008
Page 57
Supply Chain Management System Software Requirements Specification
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Confidential
Version: 1.1 Date: 20/12/2008
View Supply Requests Critical Less than 1 second Usually every time the supplier logins to the system. Almost daily. Database
Team#6 , 2008
Page 58
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.20.2 Sequence Diagram
3.2.21.1 View Request Details USE CASE #21 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
View Request Details To view extended details of the chosen reque st. Primary Task - The actor has logged in. Details of the chosen request are displayed. An error message is generated. Primary: Supplier
Clicking on the proper link on a certain displayed request to show its full details. Step Action 1 2 3
Confidential
He clicks on the proper link to view supply requests. A list of pending requests is listed. He clicks on the proper link on a request to display its details. Team#6 , 2008
Page 59
Supply Chain Management System Software Requirements Specification
EXTENSIONS
Step 1a
SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
Branching Action "Error!" message Branching Action
1 RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
View Request Details Critical Less than 1 second. Usually every time the supplier logins to the system. Almost daily. Database
Send Feedback on Request
3.2.21.2 Sequence Diagram
3.2.22.1 Send Feedback on Request Confidential
Team#6 , 2008
Page 60
Supply Chain Management System Software Requirements Specification
USE CASE #22 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS
Version: 1.1 Date: 20/12/2008
Send Feedback on Request The supplier states whether he can supply all the requested items or part of them and the time frame to deliver them. Primary Task - The actor has logged in. - The actor views a certain request details. A message indicating successful submission is generated. An error message is generated. Primary: Supplier
Clicking on the proper link on a certain displayed request to show its full details. Step Action 1 2 Step 1a
SUBVARIATIONS
He input his feedback and submits. A success (or error) message is displayed. Branching Action "Error!" message. Branching Action
1 RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Confidential
Send Feedback on Request Critical Less than 1 second. Usually every time the supplier logins to the system and at least one request exists. Almost daily. Database
Team#6 , 2008
Page 61
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.21.2 Sequence Diagram
3.2.23.1 Edit Profile USE CASE # 23 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
Edit Profile The customer can edit his profile. The profile contains the name of the customer, his address, contact pe rson and e-mail… etc. Primary Task - The actor has logged in. The customer profile is updated to the newly entered values. The older profile remains as is. An error message is generated. Primary: Customer Secondary: Coordinator (by use case Edit Customer) Clicking on the proper link for editing the profile. Step Action 1 2
EXTENSIONS
SUBConfidential
Step 1a
He clicks on the proper link to edit his profile. Whether he makes changes or not, when he clicks on the proper link to submit the profile values, the current values of the profile is saved and he is returned to the main menu. Branching Action Invalid input : Generating error message and discard changes. Branching Action Team#6 , 2008
Page 62
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
VARIATIONS
none Edit Profile
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Critical (some functions depend on successfulness of this UC) Must not exceed 1 sec to save the new input values. Once every 2-3 months. Database.
3.2.23.2 Sequence Diagram
3.2.24.1 Add Request USE CASE #24 Goal in Context Scope & Level Preconditions Success End Condition Failed End Confidential
Add Request Customer can add new request. Company , Summary -The Customer has logged in. - A new request is added. An error message is generated and the request is discarded. Team#6 , 2008
Page 63
Supply Chain Management System Software Requirements Specification
Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
Customer , Coordinator
When the Customer clicks on the proper link for adding a request. Step Action 1 The Customer press “Add Request” 2 The Customer fills the request form. 3 The Customer will send the request to the Coordinator. Step Branching Action 1a "Error!" message Branching Action 1
Customer may use phone to request from Coordinator. The Coordinator, then, adds the request manually.
RELATED Add Request INFORMATION Priority: Top 10 minutes for request, 2 days until accept Performance Frequency 10/day Channels to actors not yet determined What if the Customer cannot add new requests? OPEN ISSUES Due Date Release 1.0 ...any other management information... Superordinates Requests Management Subordinates None
3.2.24.2 Sequence Diagram
Confidential
Team#6 , 2008
Page 64
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.25.1 View Requests USE CASE #25 View Requests Goal in Context Customer can view all his pending requests that were sent to the Coordinator. Company , Summary Scope & Level Preconditions -The Customer has logged in. Success End - The Customer views all requests. Condition An error message is generated and the request is discarded. Failed End Condition Customer, Coordinator. Primary, Secondary Actors When the Customer clicks on the proper link for adding a request. Trigger DESCRIPTION Step Action 1 The Customer press “View Requests” 2 The Customer view list of requests. EXTENSIONS Step Branching Action 1a "Error!" message SUBBranching Action VARIATIONS 1 Customer may want to refine viewed request on certain criteria. 2 Customer may want to see some older requests. RELATED INFORMATION Confidential
View Requests
Team#6 , 2008
Page 65
Supply Chain Management System Software Requirements Specification
Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
Top 3 seconds to show the list 10/day not yet determined What is the coordinator cannot view requests? Release 1.0
Manage Requests - Delete Request - Edit Request
3.2.25.2 Sequence Diagram
3.2.27.1 Edit Request
Confidential
Team#6 , 2008
Page 66
Supply Chain Management System Software Requirements Specification
USE CASE # 27 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Edit Request The Customer can edit request and notify the Coordinator. Company , Summary -The Customer has logged in. - The chosen request is edited. - The notification will send to the coordinator. An error message is generated and the request is discarded. Customer, Coordinator
When the Customer clicks on the proper link for editing a request. Step Action 1 The Customer press “Edit Request” 2 The Customer modifies the request information. 3 A notification will be sent to the Coordinator. Step Branching Action 1a "Error!" message Branching Action 1
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES
Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
Coordinator may use phone to request from suppliers Edit Request Top 10 minutes for edit, on time change 10/day not yet determined - What if the Customer cannot edit any request? - Shouldn't we disable editing requests whenever they are acknowledged by the Coordinator? Release 1.0
View Request Details None
3.2.27.2 Sequence Diagram
Confidential
Team#6 , 2008
Page 67
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.28.1 Delete Request USE CASE #28 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Confidential
Delete Request The Coordinator can delete request and notify his supplier Company , Summary -The Customer has logged in. - The Customer can delete a chosen request. - The notification will be sent to the Coordinator. An error message is generated. Customer, Coordinator
When the Customer clicks on the proper link for deleting a request. Step Action 1 The Customer press “Delete Request” 2 The information about the request will show. 3 Press “Delete” to processing the deleting 4 The Customer will send a notification to supplier Step Branching Action 1a "Error!" message Branching Action
Team#6 , 2008
Page 68
Supply Chain Management System Software Requirements Specification
1
Version: 1.1 Date: 20/12/2008
Customer may use phone to delete the request by the Coordinator.
Delete Request RELATED INFORMATION Priority: Performance 5 seconds for delete 10/day Frequency Channels to actors not yet determined What is the coordinator cannot delete requests? OPEN ISSUES Due Date Release 1.0 ...any other management information... Superordinates View Request Details None Subordinates 3.2.28.2 Sequence Diagram
3.2.29.1 Manage Customers USE CASE # 29 Goal in Context Scope & Level Preconditions Success End Confidential
Manage Customers The main customers management page that coordinator will manage all customers information Company, Summary -Must the coordinator login - The coordinator should add ,view, edit or delete customers Team#6 , 2008
Page 69
Supply Chain Management System Software Requirements Specification
Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS
An error message is generated. Coordinator , Customer
Step 1 2 3 Step 1a
SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
Action The coordinator press “Manage Customers” The coordinator use any function. The coordinator will manage all customers function. Branching Action - "Error!" message Branching Action
Manage Customers Top
What if the coordinator cannot manage cutomers? Release 1.0
Login Add Customer , View Customers
3.2.30.1 Add Customer USE CASE #30 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION Confidential
Add Customer Coordinator can add new Customer. Company , Summary -Must the coordinator login -The coordinator press “Add Customer” - The coordinator can add new customer. - Login in failed - An error message is generated. Coordinator , Cutomer
When the coordinator needs to add new customer. Step Action Team#6 , 2008
Page 70
Supply Chain Management System Software Requirements Specification
EXTENSIONS
1 2 3 Step 1a
SUBVARIATIONS
Version: 1.1 Date: 20/12/2008
The coordinator press “Add Customer” The coordinator fills the new customer form. The coordinator will send the customer to supplier Branching Action "Error!" message Branching Action
RELATED Add Customer INFORMATION Priority: Top 1 minutes for request, 2 days until accept Performance Frequency 10/day Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot add new customer? Due Date Release 1.0 ...any other management information... Customers Management Superordinates Subordinates None 3.2.30.2 Sequence Diagram:
3.2.31.1 View Customers USE CASE #31 Goal in Context Confidential
View Customers coordinator can view a list of all customers. Team#6 , 2008
Page 71
Supply Chain Management System Software Requirements Specification
Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Company , Summary -Must the coordinator login - The coordinator can show all customers. - Login in failed - The coordinator cannot view all customers. Coordinator , Customer
When the coordinator needs to view customers and clicks on the proper link to that function. Step Action 1 The coordinator press “View Customers” 2 The coordinator view list of customers. Step Branching Action 1a "Error!" message Branching Action 1
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
Coordinator may want to see refined list on certain criteria only. View Customers Top 10 seconds to show the list 10/day not yet determined What if the coordinator cannot view customers? Release 1.0
Manage Customers View Customer Details
3.2.31.2 Sequence Diagram:
3.2.32.1 View Customer Details USE CASE #32 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Confidential
View Customer Details Coordinator can show the details of any customer that he chose. Company , Summary -Must the coordinator login -The coordinator press “View Customer Details” - The coordinator can show the details of a customer. -
The coordinator cannot show the details of a customer.
Team#6 , 2008
Page 72
Supply Chain Management System Software Requirements Specification
Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
Coordinator , Customer
When the coordinator need to view the details of a customer. Step Action 1 The coordinator press “View Customer Details” 2 The coordinator views the details of a customer. Step Branching Action 1a "Error!" message Branching Action
View Customer Details Middle 10 seconds to show the details of a customer. 10/day not yet determined What is the coordinator cannot view the details of a customer? Release 1.0
View Customers Delete Customer, Edit Customer
3.2.31.2 Sequence Diagram:
Confidential
Team#6 , 2008
Page 73
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.33.1 Edit Customer USE CASE # 33 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date Confidential
Edit Customer The Coordinator can edit customer him. Company , Summary -Must the coordinator login - The coordinator can edit exist customer. - Login in failed - An error message is generated. Coordinator , Customer
When the coordinator needs to edit any exist c ustomer. Step Action 1 The coordinator press “Edit Customer” 2 The coordinator modifies the request information. 3 The coordinator will send a notification to the customer. Step Branching Action 1a "Error!" message Branching Action
Edit Customer Top 1 minutes for edit, on time change 10/day not yet determined What if the Coordinator cannot edit any customer? Release 1.0 Team#6 , 2008
Page 74
Supply Chain Management System Software Requirements Specification
...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
ViewCustomer Details None
3.2.33.2 Sequence Diagram sd CoorEditCustomer
Coordinator
C Customer
Edit customer()
Customer Form()
Update Customer()
Custome r Updated()
3.2.34.1 Delete Customer USE CASE #34 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Confidential
Delete Customer The coordinator can delete a certain customer Company , Summary -Must the coordinator login - The coordinator can delete exist customer. - The customer will be notified by option. - Login in failed - An error message is generated. Coordinator , Customer
When the coordinator needs to delete any exist customer. Step Action 1 The coordinator press “Delete Customer” 2 The information about the customer will show. 3 Press “Delete” to processing the deleting 4 The coordinator will send a notification to the customer on option. Step Branching Action 1a "Error!" message Branching Action
Team#6 , 2008
Page 75
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
RELATED Delete Customer INFORMATION Priority: 1 minute for delete Performance Frequency 10/day Channels to actors not yet determined What is the coordinator cannot delete customer? OPEN ISSUES Due Date Release 1.0 ...any other management information... View Customer Details Superordinates None Subordinates 3.2.34.2 Sequence Diagram
3.2.35.1 Manage Suppliers USE CASE # 35 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION Confidential
Manage Suppliers The main suppliers management page that coordinator will manage all suppliers information Company, Summary -Must the coordinator login The coordinator should add ,view, edit or delete his suppliers. An error message is generated. Coordinator , Supplier
Step
Action Team#6 , 2008
Page 76
Supply Chain Management System Software Requirements Specification
EXTENSIONS
1 2 3 Step 1a
SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
The coordinator press “Manage Suppliers” The coordinator use any function. The coordinator will manage all suppliers function. Branching Action - "Error!" message Branching Action
Manage Suppliers Top
What if the coordinator cannot manage suppliers? Release 1.0
Login Add Supplier, View Supplier
3.2.36.1 Add Supplier USE CASE #36 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
Confidential
Add Supplier Coordinator can add new Supplier Company , Summary -Must the coordinator login - The coordinator can add new Supplier. - Login in failed - An error message is generated. Coordinator , Supplier
When the coordinator needs to add new Supplier. Step Action 1 The coordinator press “Add Supplier” 2 The coordinator fills the new Supplier form. 3 The coordinator will send the Supplier to supplier Step Branching Action 1a "Error!" message Branching Action
Team#6 , 2008
Page 77
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
Add Supplier RELATED INFORMATION Top Priority: Performance 1 minutes for application, 2 days until accept Frequency 10/day Channels to actors not yet determined OPEN ISSUES What is the coordinator cannot add new Supplier? Release 1.0 Due Date ...any other management information... Superordinates Suppliers Management Subordinates None 3.2.36.2 Sequence Diagram
3.2.37.1 View Suppliers USE CASE #37 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION Confidential
View Suppliers coordinator can view a list of all Suppliers. Company , Summary -Must the coordinator login - The coordinator can show all Supplier. - Login in failed - The coordinator cannot view all Suppliers. Coordinator , Supplier
When the coordinator needs to view Suppliers and clicks on the proper link to that function. Step Action Team#6 , 2008
Page 78
Supply Chain Management System Software Requirements Specification
EXTENSIONS
Version: 1.1 Date: 20/12/2008
1 2 Step 1a
The coordinator press “View Suppliers” The coordinator view list of Suppliers. Branching Action "Error!" message Branching Action
1
Coordinator may want to see refined list on certain criteria only.
SUBVARIATIONS
View Suppliers
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Top 10 seconds to show the list 10/day not yet determined What if the coordinator cannot view Suppliers? Release 1.0
Manage Suppliers View Supplier Details
3.2.37.2 Sequence Diagram sd CoordViewSuppliers
Coordinator
S Supplier
view suppl iers()
li st of suppl iers is returned()
3.2.38.1 View Supplier Details USE CASE #38 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Confidential
View Supplier Details Coordinator can show the details of any Supplier that he chose. Company , Summary -Must the coordinator login -The coordinator press “View Supplier Details” - The coordinator can show the details of a Supplier. -
The coordinator cannot show the details of a Supplier.
Coordinator , Supplier Team#6 , 2008
Page 79
Supply Chain Management System Software Requirements Specification
Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
When the coordinator need to view the details of a Supplier. Step Action 1 The coordinator press “View Supplier Details” 2 The coordinator views the details of a Supplier. Step Branching Action 1a "Error!" message Branching Action
View Supplier Details Middle 10 seconds to show the details of a Supplier. 10/day not yet determined What is the coordinator cannot view the details of a Supplier? Release 1.0
View Supplier Delete Supplier, Edit Supplier
3.2.38.2 Sequence Diagram:
Confidential
Team#6 , 2008
Page 80
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.2.39.1 Edit Supplier USE CASE # 39 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Confidential
Edit Supplier The Coordinator can edit Supplier and notify him (on option.) Company , Summary -Must the coordinator login - The coordinator can edit exist Supplier. - Login in failed - An error message is generated. Coordinator , Supplier
When the coordinator needs to edit any exist S upplier. Step Action 1 The coordinator press “Edit Supplier” 2 The coordinator modifies the Supplier information. 3 The coordinator will send a notification to the Supplier. Step Branching Action 1a "Error!" message Branching Action
Edit Supplier Top 1 minutes for edit, on time change 10/day not yet determined What if the Coordinator cannot edit any Supplier? Team#6 , 2008
Page 81
Supply Chain Management System Software Requirements Specification
Due Date ...any other management information... Superordinates Subordinates
Version: 1.1 Date: 20/12/2008
Release 1.0
View Supplier Details None
3.2.39.2 Sequence Diagram
3.2.40.1 Delete Supplier USE CASE #40 Goal in Context Scope & Level Preconditions Success End Condition Failed End Condition Primary, Secondary Actors Trigger DESCRIPTION
EXTENSIONS SUBVARIATIONS
RELATED INFORMATION Priority: Performance Frequency Channels to actors OPEN ISSUES Due Date ...any other management information... Superordinates Confidential
Delete Supplier The coordinator can delete a certain Supplier Company , Summary -Must the coordinator login - The The coor coordi dina nato torr can del delet etee exis existt Suppl Supplie ier. r. - The The Supp Suppli lier er wil willl be not notif ifie ied d by opt optio ion. n. - Login in failed - An erro errorr mes messa sage ge is gene genera rate ted. d. Coordinator , Supplier
When the coordinator needs to delete any exist Supplier. St e p Action 1 The coordinato ator press “Dele elete Suppli plier” 2 The inform format atio ion n abou aboutt the cust custom omeer will ill sho show. 3 Press “D “Delete” to to pr processing th the de deleting 4 The The coo coord rdin inat ator or will will send send a not notif ific icat atio ion n to to the the Supp Suppli lier er on option. St e p Branching Action 1a "Error!" me message Branching Action
Delete Supplier
1 minute for delete 10/day not yet determined What is the coordinator cannot delete Supplier? Release 1.0
View Supplier Details Team#6 , 2008
Page 82
Supply Chain Management System Software Requirements Specification
Subordinates
Version: 1.1 Date: 20/12/2008
None
3.2.40.2 Sequence Diagram
Confidential
Team#6 , 2008
Page 83
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
3.3 Performance Requirements The system must handle at least 100 concurrent users and their operations. The system must accomplish 90% for transactions in less than 1 second. This is due to the nature of data, which is only text information that does not usually exceed 50 KB per transaction.
3.4 Logical Database Requirements The DB tables shall reflect following: - Coordinator - Customer - Supplier - Resource Location - Item - Request
3.5 Design Constraints 3.5.1 Programming language: Our System will be web based system which we will use a web developing language. We will use ASP.NET and C# languages. The system has to be designed on .NET Framework 3.5 using Visual Studio family. 3.5.2 Database:
The system will use MS SQL for our database. 3.5.3 .5.3
Soft Softw ware are Pro Proce cesss:
The system shall follow the Waterfall software process model. Also the system shall be designed in an Object Oriented approach so that future features can be easily integrated with the system.
3.5.4 .5.4
Ejad Ejada a fram framew ewo ork: rk:
The system has to use the Ejada .Net frame work and also our system will integrate with two modules in Ejada. 3.6 Software System Attributes 3.6.1
Reliability All data will be backed-up everyday automatically and also the system administrator can back-up the data as a function for him. Also if any errors, fault or failures happen the system will detected and inform the user about problems and also if there is any transaction with the database and in that time happen no action to the data and the system will back to the previous state of database. Also our system will cover the quality assurance. 3.6. .6.2
Availability The system has to be available 100% of the time. Once there is a fatal error, the system should give understandable feedback to the user.
Confidential
Team#6 , 2008
Page 84
Supply Chain Management System Software Requirements Specification
3.6.3
Version: 1.1 Date: 20/12/2008
Security
The system have only three roles for coordinators , suppliers and customers only that make our system secure access online and these authentications will prevent and illegal access. 3.6.4 .6.4
Mai Mainta ntainabi nabillity
The system is designed in modules where errors can be detected and fixed easily. This makes it easier to install updates and new functionality if required. 3.6.5
Portability
The system can operate in any of the latest Microsoft operating systems with the latest .Net framework. Due to the web based nature of the system, the host machine must also have Microsoft IIS installed
4. Change Management Process Every change in the SRS will be done by the developing team and it is updated in the SRS review report which contains all the information of the change shush as change date, author, the change is applied on what , and why the changed is applied.
Confidential
Team#6 , 2008
Page 85
Supply Chain Management System Software Requirements Specification
Version: 1.1 Date: 20/12/2008
Appendix Use Case Diagrams uc Use Case Model
UC36: Add Supplier
UC30: Add Customer
UC33: Edit Customer «extend»
UC32: View Customer Details
UC40: Delete Supplier
UC39: Edit Supplier
«extend»
«extend»
«extend»
«extend»
«extend» UC34: Delete Customer UC31: View Customers
UC29: Manage Customers
«extend»
UC35: Manage Suppliers
«extend»
«extend»
UC38: View Supplier Details
UC37: View Suppliers
«extend»
UC2: Add Request
UC14: Add Location
UC1: Manage Requests
UC13: Manage Resource Locations
«extend»
«extend»
UC4: View Request Details
«extend»
Coordinator «extend»
«extend»
UC16: View Loca tion Details
UC3: View Requests «extend»
«extend»
«extend»
UC15: View Locations
«extend»
UC7: Manage Items
«precedes»
UC5: Edit Request
UC6: Delete Request
«extend» UC18: Delete Location
«extend»
UC17: Edit Location
UC8: Add Item UC9: View Items
«extend»
UC11: Edit Item «extend» UC23: Edit Profile
UC10: View Item Details
UC12: Delete Item
«extend»
UC19: Edit Profile
UC20: View S upply Requests
UC24: Add Request
UC21: View Request Details
UC25: View Requests UC28: Delete Request Customer
Supplier «extend»
«extend» «extend» UC26: View Request Details
Confidential
«extend»
UC27: Edit Request
Team#6 , 2008
UC22: Send Feedback on Request
Page 86