Solved by verified expert:This assignment gives you the opportunity to apply a systematic approach to translate requirements into a high-level logical system design.This assignment specifically addresses the following course outcomes to enable you to: apply a systematic approach to translate requirements into an executable systems designeffectively communicate with stakeholders to determine, manage, and document business requirements throughout the SDLCPlease be a thorough as possible with requirement and system design specifications
stage_3___system_design_specificationv2.docx
moody_stage_2__2_.docx
Unformatted Attachment Preview
Stage 3: System Design Specification
Before you begin this assignment, be sure you have read the Case Study and all assignments for this
class, especially Stage 4: Final System Report. The feedback you received on your Stage 1 and Stage 2
assignments should be reviewed and used as you proceed with Stage 3.
Purpose of this Assignment
This assignment gives you the opportunity to apply a systematic approach to translate requirements into
a high-level logical system design. This assignment specifically addresses the following course outcomes
to enable you to:
•
•
apply a systematic approach to translate requirements into an executable systems design
effectively communicate with stakeholders to determine, manage, and document business
requirements throughout the SDLC
Assignment
The results of your systems analysis and design work in this class will be documented in a Final System
Report. The purpose of the Report is to inform management of your system proposal and gain approval
to proceed with the project. The Report will be developed and submitted in stages, which will be
compiled at the end of class into the Final System Report. Review the outline of the Final System Report
in the Stage 4 Assignment description. Note that it contains the analysis of the problem(s) and
requirements, and proposes what kind of a system solution is needed. It does not propose a specific
solution, but it does recommend why and how the organization should acquire the solution.
Following the Requirements Specification (Stage 2 assignment), the next step is to develop the System
Design Specification. The System Design Specification builds on the Requirements Specification to
illustrate how the files/database(s) will be laid out, how the output (forms, reports, and/or screens) and
input (forms and/or screens) should be designed. As you develop this assignment, you should refer to
your Stage 2 Requirements Specification (and the feedback you received) and use the inputs and outputs
you listed to create the input and output layouts and the file/database design.
All of the information you need to complete the projects in this class is not provided in the case study. In
the discussion area of the classroom, there is a discussion titled “Case Study Interview Questions” where
you can pose questions about the case study, as if you were interviewing the people in the case study
organization. Any information that you need that is not included in the case study should be asked about
in this discussion. Responses from the faculty member on behalf of the case study organization will be
available for everyone in the class.
Use the case study and the Case Study Interview Questions discussion, along with your Stage 2
Requirements Specification (including the feedback received), and resources below, to create a System
Design Specification in the format shown below. Include your corrected Stage 2 Requirements
Specifications as the first part of this assignment. Approximate lengths for each section of the Systems
Design Specification are provided as a guideline; be sure to provide all pertinent information. The
sources of explanatory materials can be found in the Week 5 Content readings.
Stage 3: System Design Specification
1
Requirements Specification
Include your Requirements Specification from Stage 2, with corrections from the feedback
included. This will establish the context for your System Design Specification to follow.
System Design Specification
I.
II.
III.
IV.
Introduction. Provide an appropriate introduction to this document. (one paragraph)
Output Layout. Begin with the three outputs listed in your Requirements Specification. For
each of them, create a diagram or table illustrating what the output would look like. (use a
short paragraph to introduce this section and each diagram, table or illustration should use
about ½ of a page)
A. Output Layout #1.
B. Output Layout #2.
C. Output Layout #3.
Input Layout. Using the data elements listed in your Requirements Specification, create a
diagram or table illustrating what the input screen would look like for each of the three sets
of input. (use a short paragraph to introduce this section and each diagram, table or
illustration should use about ½ of a page)
A. Input Layout #1.
B. Input Layout #2.
C. Input Layout #3.
File/database Design ERDs. For each of the three sets of outputs and inputs, create an
Entity Relationship Diagram showing how the data elements are related to each other [see
an explanation at http://www.cs.uregina.ca/Links/class-info/215/erd/, and use the
formatting specified in the example]. Depending on the inputs and outputs identified, there
may be some overlap of the data elements in the ERDs; a separate ERD should be developed
for each pair of inputs/outputs. (use a short paragraph to introduce this section, and each
ERD should be on one page)
A. File/database Design ERD #1.
B. File/database Design ERD #2.
C. File/database Design ERD #3.
Submitting Your Assignment
Submit your Requirements Specification and System Design Specification as one document via your
Assignment Folder as Microsoft Word document, or a document that can be ready using MS Word, with
your last name included in the filename. Use the Grading Rubric below to be sure you have covered all
aspects of the assignment.
GRADING RUBRIC:
Stage 3: System Design Specification
2
Criteria
Introduction
Output
Layouts
Input Layouts
File/Database
Design ERDs
90-100%
80-89%
70-79%
60-69%
< 60%
Far Above
Standards
Above Standards
Meets Standards
Below Standards
Well Below
Standards
5 Points
4 Points
3.5 Points
3 Points
0-2 Points
The corrected
Requirements
Specification is
included along with
a well-written
introduction to the
Systems Design
Specification;
demonstrates a
sophisticated level
of writing.
The corrected
Requirements
Specification is
included along with
an appropriate
introduction to the
Systems Design
Specification;
demonstrates clear
writing.
The corrected
Requirements
Specification is
included along
with an
introduction to the
Systems Design
Specification.
The corrected
Requirements
Specification
and/or the
introduction to
the Systems
Design
Specification may
not be included
or may not be
complete.
The corrected
Requirements
Specification
and
introduction to
the Systems
Design
Specification
are not
included, or
little effort is
demonstrated.
27-30 Points
24-26 Points
21-23 Points
18-20 Points
0-17 Points
30
Three output
layouts are clearly
and logically
presented; and
very clearly relate
to the output
requirements
previously defined.
Demonstrate a
sophisticated level
of analysis.
27-30 Points
Three output
layouts are clearly
presented; and
clearly relate to the
output
requirements
previously defined.
Demonstrate
accurate analysis.
Three output
layouts are
presented and
relate to output
requirements
previously defined.
Fewer than three
output layouts
may be provided,
and/or they may
not be
appropriate to
the previously
defined output
requirements.
24-26 Points
21-23 Points
One or no
output layouts
are provided,
may not relate
to the
previously
defined output
requirements,
or little effort
is
demonstrated.
0-17 Points
30
Three input layouts
are clearly and
logically presented;
and very clearly
relate to the input
requirements
previously defined.
Demonstrate a
sophisticated level
of analysis.
Three input layouts
are clearly
presented; and
clearly relate to the
input requirements
previously defined.
Demonstrate
accurate analysis.
Three input
layouts are
presented and
relate to input
requirements
previously defined.
27-30 Points
24-26 Points
21-23 Points
18-20 Points
One or no
input layouts
are provided,
may not relate
to the
previously
defined input
requirements,
or little effort
is
demonstrated.
0-17 Points
30
Three Entity
Relationship
Diagrams may
not be included,
Fewer than
three Entity
Relationship
Diagrams are
Three Entity
Relationship
Diagrams are
correctly
Three Entity
Relationship
Diagrams are
correctly
Stage 3: System Design Specification
Three Entity
Relationship
Diagrams are
adequately
18-20 Points
Fewer than three
input layouts may
be provided,
and/or they may
not be
appropriate to
the previously
defined input
requirements.
Possible
Points
5
3
Format
constructed,
logical, appropriate
to the
inputs/outputs, and
demonstrate a
sophisticated level
of analysis.
5 Points
constructed,
logical, appropriate
to the
inputs/outputs, and
demonstrate
accurate analysis.
constructed, and
appropriate to the
inputs/outputs.
and/or may not
be appropriate to
the
inputs/outputs.
4 Points
3.5 Points
3 Points
Submission reflects
effective
organization and
sophisticated
writing; follows
instructions
provided; uses
correct structure,
grammar, and
spelling; presented
in a professional
format; any
references used are
appropriately
incorporated and
cited using APA
style.
Submission reflects
effective
organization and
clear writing;
follows instructions
provided; uses
correct structure,
grammar, and
spelling; presented
in a professional
format; any
references used are
appropriately
incorporated and
cited using APA
style.
Submission is
adequate, is
somewhat
organized, follows
instructions
provided; contains
minimal grammar
and/or spelling
errors; and follows
APA style for any
references and
citations.
Submission is not
well organized,
and/or does not
follow
instructions
provided; and/or
contains
grammar and/or
spelling errors;
and/or does not
follow APA style
for any
references and
citations. May
demonstrate
inadequate level
of writing.
not provided,
are not
appropriate to
the inputs/
outputs or
little effort is
demonstrated.
0-2 Points
Document is
extremely
poorly written
and does not
convey the
information.
TOTAL
Points
Possible
Stage 3: System Design Specification
5
100
4
Running head: SYSTEM SPECIFICATION
1
Stage 2: Precision Electronic Parts (PEP) Requirements Specification Document
Ajani E. Moody
UMUC
16 June 2019
SYSTEM SPECIFICATION
2
Introduction
The purpose of the proposed system is to ensure that customers' purchase activities and
PEP’s business transactions are accurately tracked and documented. The proposed system is
required to be able to generate any invoices, customer information, billing, and other important
reports. Due to changing business needs, PEP needs an updated system that will ensure that all
these requirements are met.
Functional Requirements
Every system is designed following a set of requirements in a bid to satisfy the
requirements of the end user. The requirements specification process will ensure that the system
runs efficiently, without error, and ensures that the system follows the defined set of requirements.
These defined requirements will include the needs of the stakeholders, the customers, and what
the primary function of the system. The requirements specification process is divided into three
categories based on the system's functions. The categories include inputs, outputs, and processing
requirements. The proposed system must be scalable in order to satisfy all the needs of the
customers as well as other stakeholders. Again, the system should ensure high levels of efficiency.
These are key factors and will be used to measure if the proposed system is deemed successful or
a failure.
Output requirements
i. The proposed system will provide billing and purchase receipts to the customers
ii.
The proposed system will provide complete financial statements to include
accounts receivable and past due reports to both the stakeholders and the
customers
iii.
The proposed system will provide updated invoices during the billing process
SYSTEM SPECIFICATION
3
Input requirements
The proposed system will allow input of orders from customers and insert the
i.
data in the financial statements.
ii.
The proposed system will allow information related to the accounts receivable.
iii.
The proposed system will generate data in regards to PEP business transactions
and record the data it their respective accounts to allow invoicing.
Processing Requirements
i.
The system shall process the profits or loss made by the business.
ii.
The system shall process all the transactions taking place in the business. (In and out
of the business).
iii.
The system shall process any sales and purchases taking place in the business.
Technical Requirements
Besides the functional requirements identified in the earlier sections of this report, there
are still other requirements that the system should meet to ensure that the project is a success.
Technical requirements should still be identified in the system. These requirements are divided
into five categories based on the aspect each category covers in the system. The categories are
security, system control, performance and business continuity.
Security Requirements
The customer's data should be secure while in the system. To ensure such security, the
system will incorporate the following security measures.
a) Firewall - A firewall acts as the first line of defense for any system. The firewall
will depend on the type of system's architecture. Access Control List is used to
prevent network's unauthorized access.
SYSTEM SPECIFICATION
4
b) Encryption - Encrypting the system's data will ensure that its confidentiality is not
compromised. The data should be encrypted at all times, whether it is at use, rest or
transit. This process will involve an algorithm that will convert the plain text to
cypher texts.
c) Access control - Access to the system shall be limited to minimize the security
threats and modifications. The system shall be accessed based on the need-to-know
methodology.
d) Anti-malware software - Every system faces the risk of malicious codes. To
overcome this challenge, anti-malware software will ensure that the system is free
from such codes.
e) Network Security - Network devices will be used to filter traffic within the
network. The devices will protect, inspect, allow or block traffic. This type of
security measure will protect the system from unauthorized network access.
f) Intrusion Detection System (IDS) - The IDS shall ensure that any vulnerability in
the system is detected at early stages.
System Control Requirements
Access should be only granted to authorized personnel. The following are the system access
control requirements for the proposed system.
i.
Access to the system will only be granted by the system's administrator.
ii.
No information shall be displayed without identification and authentication of the users.
iii.
The system's preferences should be preset before the system is handed over to the users;
any changes must be done through the system admin or the IT manager.
Performance Requirements
SYSTEM SPECIFICATION
5
These requirements will ensure that a high level of efficiency and effectiveness of the system
is maintained. This should result in reduction the time it takes to process the business transactions.
These requirements include:
i.
The system must be able to process transactions regardless of the amount of orders.
ii.
The system must be able to quickly and efficiently process and produce the business's
invoice and reports.
iii.
The system must have scalability to accommodate increased number of transactions
within the business.
Business Continuity Requirements
This set of requirements will ensure that the system is resilient to failure and is able to quickly
recover business functions and operations in case of business disruptions from system failure or
cyber security risks/attacks. These requirements include:
i.
There must be off-site data backups in case of system failure.
ii.
There must be regular vulnerability scan to ensure that threats and vulnerabilities are
detected at early stages.
iii.
The system must ensure that all data is recovered in case of failure.
System Scope Diagrams
Some work must be done to pass on a deliverable, a result, or a service with the set of
predefined features and limits. This is referred as project scope. System scope diagrams ensure
that the project follows the correct order as well as ensuring that the scope creep is controlled.
SYSTEM SPECIFICATION
6
Context Diagram
A context diagram is a flow-like diagram that is used to establish/show the system
boundaries. It shows how the information between the system and external entities flows. The
diagram will contain.
a. The name of the process
b. Entity under investigation
Data Flow Diagram
A data flow diagram is a system modeling diagram which shows a step wise flow of data
throughout the proposed system. This diagram will give a visual representation of how the data
will flow within the business organization. In simpler terms, the diagram will show how data (from
login to shipping) will flow.
SYSTEM SPECIFICATION
7
Data Flow Diagram
Use Case Diagram
A use case diagram provides a representation of how the interaction of different actors and
the system will look. This type of system scope diagram helps the end-user visualize the system
in its final state. Use case diagrams show how the system and other external actors will interact.
The use case will have the following.
Actors – These are external entities to the system. The actors in this case will be;
c. New customers
d. Regular customers
e. Service Authentication
f. Identify provider
SYSTEM SPECIFICATION
8
g. Payment department
h. Inventory department
i. Product tracking and billing
Order of Events
•
Regular customers login into the system/new customers register into the system
•
Service authentication determines identity and grants access
•
Customers search for products
•
Customers add products to cart
•
Customers order products
•
Customers choose the payment options
•
Payment department processes payment
•
Inventory department processes the invoices for the order as well as the billing information
•
Product tracking and billing provides shipping information to the customer
•
The product is shipped to the customer
SYSTEM SPECIFICATION
9
Use Case Diagram
Process Models
English Structure
English structure is used in describing the project’s iteration, selection, and sequences.
English structure is similar to other programming languages except no syntax rules are applied.
With the proposed system, operations will be managed so that they eliminate stagnant processes
SYSTEM SPECIFICATION
10
in case of failure. The English structure in this case will show the categories of customers who
qualify for discounts. It is as follows;
IF
(the customers buy 5 or more products)
THEN
(Allow 2% or more discount on the purchased products)
ELSE
(Don’t allow discount)
IF
(payment is overdue 30 or more days)
THEN
(Send collection and no discount)
END IF
(Payment done within 30 days)
Decision Table
A decision table is a matrix that groups similar actions and conditions together. Overlaps
and gaps in projects are usually identified using a decision table. The decision table in this case
will assist the business organization in setting up the correct rules for managing and easing the
business processes.
SYSTEM SPECIFICATION
11
KEY:
•
Z – New customer.
•
E – Existing customer.
•
N – No
•
Y – Yes.
Rules
1- 4
Conditions
Customers
5 -9
10 – 14
15 -19
20 -24
25 – 29
E
E
Z
E
Z
N
N
Y
Y
N
(Existing/New)
Collections
Payment done
after 30 or more
days.
SYSTEM SPECIFICATION
Payment done
12
Y
N
Y
Y
N
after 60 or more
days.
Actions
No discount
allowed
Discount
Y
Y
allowed (2%)
Discount
Y
Y
allowed (5%)
Discount
allowed (10%)
Y
SYSTEM SPECIFICATION
13
Decision Tree
A decision tree is a yes/no based graph that follows certain rules and conditions to make
certain decisions for an organization. The decision tree can be generated from the decision table.
The decision tree for the proposed system is as follows;
SYSTEM SPECIFICATION
14
References.
Karl, W. (2017). Defining project scope. Conte …
Purchase answer to see full
attachment
