Replace this Line with the Title of Your Paper Your Name Goes Here American Public University System System Design Specification Table of Contents 1. Management summary a. Summary of requirements b. Development to date c. Provides a current status report d. Summarizes project costs and benefits e. Implementation schedule highlights f. Any issues that management will need to address 2. System Components a. System 3. System Environment a. Constraints b. Requirements c. Hardware (Storage, Input / Output Devises) d. Systems software e. Security 4. Implementation requirements a. Specify start-up processing b. Initial data entry or acquisition c. User training requirements d. Software test plans 5. Time and cost estimates a. Detailed schedules b. Cost estimates, c. Staffing requirements d. Total costs-to-date 6. Additional material a. Other material 1. Management Summary 2. System Components 3. System Environment 4. Implementation Requirements 5. Time and cost estimates 6. Additional Material System Design Specification Guide The system design specification presents the complete system design for an information system and is the basis for the presentations that complete the systems design phase. Following the presentations, the project either progresses to the systems development phase, requires additional systems design work, or is terminated. System Design Specification Table of Contents 1. Management summary (20 pts.) a. Summary of requirements b. Development to date c. Provides a current status report d. Summarizes project costs and benefits e. Implementation schedule highlights f. Any issues that management will need to address 2. System Components (40 pts.) a. System: This section contains the complete design for the new system, including the user interface, outputs, inputs, files, databases, and network specifications. You should include source documents, report and screen layouts, DFDs, and all other relevant documentation. You also should include the requirements for all support processing, such as backup and recovery, start-up processing, and file retention. If the purchase of a software package is part of the strategy, you must include any interface information required between the package and the system you are developing. If you use a CASE design tool, you can print design diagrams and most other documentation directly from the tool. 3. System Environment (15 pts.) a. Constraints, or conditions, affecting the system. Examples of operational constraints include transaction volumes that must be supported, data storage requirements, processing schedules, reporting deadlines, and online response times. b. Requirements that involve operations c. Hardware (Storage, Input / Output Devices) d. Systems software, (Interface, Communications or data exchange) e. Security 4. Implementation requirements (10 pts.) a. Specify start-up processing b. Initial data entry or acquisition c. User training requirements d. Software ...

1. Replace this Line with the Title of Your Paper
Your Name Goes Here
American Public University System
System Design Specification
Table of Contents
1. Management summary
a. Summary of requirements
b. Development to date
c. Provides a current status report
d. Summarizes project costs and benefits
e. Implementation schedule highlights
f. Any issues that management will need to address
2. System Components
a. System
3. System Environment
a. Constraints
b. Requirements
c. Hardware (Storage, Input / Output Devises)
d. Systems software
e. Security
4. Implementation requirements
a. Specify start-up processing
b. Initial data entry or acquisition

2. c. User training requirements
d. Software test plans
5. Time and cost estimates
a. Detailed schedules
b. Cost estimates,
c. Staffing requirements
d. Total costs-to-date
6. Additional material
a. Other material
1. Management Summary
2. System Components
3. System Environment
4. Implementation Requirements
5. Time and cost estimates
6. Additional Material
System Design Specification Guide
The system design specification presents the complete system
design for an information system and is the basis for the
presentations that complete the systems design phase. Following
the presentations, the project either progresses to the systems
development phase, requires additional systems design work, or
is terminated.
System Design Specification
Table of Contents
1. Management summary (20 pts.)
a. Summary of requirements
b. Development to date
c. Provides a current status report
d. Summarizes project costs and benefits
e. Implementation schedule highlights
f. Any issues that management will need to address
2. System Components (40 pts.)
a. System: This section contains the complete design for the
new system, including the user interface, outputs, inputs, files,

3. databases, and network specifications. You should include
source documents, report and screen layouts, DFDs, and all
other relevant documentation. You also should include the
requirements for all support processing, such as backup and
recovery, start-up processing, and file retention. If the purchase
of a software package is part of the strategy, you must include
any interface information required between the package and the
system you are developing. If you use a CASE design tool, you
can print design diagrams and most other documentation
directly from the tool.
3. System Environment (15 pts.)
a. Constraints, or conditions, affecting the system. Examples of
operational constraints include transaction volumes that must be
supported, data storage requirements, processing schedules,
reporting deadlines, and online response times.
b. Requirements that involve operations
c. Hardware (Storage, Input / Output Devices)
d. Systems software, (Interface, Communications or data
exchange)
e. Security
4. Implementation requirements (10 pts.)
a. Specify start-up processing
b. Initial data entry or acquisition
c. User training requirements
d. Software test plans
5. Time and cost estimates (15 pts.)
a. Detailed schedules
b. Cost estimates,
c. Staffing requirements
d. Total costs-to-date
6. Additional material
a. Other material can be included at the end of the system
design specification. In this section, you might insert documents

4. from earlier phases if they would be helpful to readers.
Case Study Worksheet and Template
Preliminary Investigation and Requirements Report Template
Version 0.0: [1/1/2016]
Presented by: [Steven Vincent]Worksheet

5. Client approval: Yes No
Note whether your case study needs to be ready in time for a
specific event:
Date: Event:
Template
Case Study for [Club IT]General Information
Company profile
Ruben Keys and Lisa Tejada are the owners and operators of
Club IT; a popular downtown nightclub that offers several
products and services. Key products and services include:
6,000 SQFT facility with 600 SQFT dance floor and seating
capacity for 220 people
Nineteen additional staff members; Assistant manager(1),
Bartender(4), Waitstaff(6), Stewards(2), Short-order cooks(2),
Security(4)
Kitchen for appetizers and short orders; food menu boasting 6
ordering options
Bar with four pour stations
Various merchandise items; T-shirt(s), Cap(s), Mug(s), and Shot
Glasses(s)
Plays Hip-hop, Techno, Electronica, MP3 and live music with
coordinate calendarBusiness situation
Club IT mission statement is as follows: "We, Ruben and Lisa,
offer you live music, DJ's, dance space and refreshments that
suit your lifestyle. You are our friends, and we seek to build a
community that meets regularly at Club IT." To meet this
mission the owners need to be able to provide services in a
timely and efficient manner. Ruben and Lisa recognize they
have some key problems with trying to accomplish this. As a
result they are revamping some of their business techniques to
improve servicing, purchasing, inventorying, and generalized

6. data management and tracking.Technical situation
Club IT is operating on minimal and outdated hardware and
software components. There system capabilities include:
Hardware:
Pentium Processor
1GB of Ram
Ethernet Adapter
17’ Color Display
High-speed modem with Comcast ISP
Software:
Windows XP Professional
MS Office
MS Access
MS Excel
After evaluating their systems the owners have noted several
perceived problems including tracking inventory ordering and
levels, the ability to print trend data reports, and system
security. Club IT wishes to employ a perpetual inventory system
that adjusts inventory levels the moment a waitress orders
something. They would also like the ability to generate reports
showing trend data such as the sale of different items, if a
particular waitress had higher sales, or if time of the day had an
effect on sales of different items. Finally the users want to
make sure no one has the ability to gain access to their data.
Problem or Opportunity
Project Scope and Constraints
Project Scope
The Must Do, Should Do, Could Do, and Won’t Do was
reviewed upon initial owner interview and will be revisited at
various times to ensure the business objective is constantly met.
As for now the project scope is to do these three things while
remaining cost effective:
1.) Install an order entry system must be implemented with the
ability to forward transactions to data monitoring services and

7. print transaction receipts.
2.) Create a system linked to the order entry system that adjusts
inventory levels the moment an article is ordered by a staff
member. The system must have the ability to generate
automatic inventory orders for ingredients that fall below the
acceptable stock inventory count.
3.) Develop independent intrinsic database systems that can
track the sale of different items, if a particular waitress had
higher sales, or if time of the day had an effect on sales of
different items. Databases must have the ability to
communicate with the order entry system and inventory system
as well as be able to print reports or export to email as desired
by user.
4.) Ensure system data and security integrity for compromise.
Project Creep
Club IT is a 6000 SQFT facility with endless possibilities for
advancement both in terms of business and technology. It is
conceivably feasible that in the future the owners will want to
expand or the technician implements more technology than is
desired. In any case, in the time of project expansion Project
Scope must be reiterated or project creep is a very real
possibility. Inventory processes could sway if not
reprogrammed, data management can become less effective with
too much information, and generalized system overload are all
issues to keep an eye on.
Constraints
The present constraints were the things identified by the project
scope; install a POS, implement a Perpetual Inventory System,
and create databases for data trend analysis. Future constraints
could be discussed at a later time if the owners decide to
expand. Note, all the constraints have come at the request of
the owners. No government regulations, state sanctions, or
other outside external forces are to be considered at this time.

8. Perform Fact-Finding
A meeting was setup with both owners to conduct an interview
in order to find out pertinent facts. The questions asked during
the interview are listed below. Once the desired information
was found out a diagram was created in order to illustrate
current process. That too is listed below.
Interview Questions:
1.) Can you give me a brief background about yourselves as
well as the history of Club IT?
2.) Can you also give me some dynamics about Club IT?
Building Size? Staff? Products and services?
3.) What are the business goals that this project is aiming to
achieve?
4.) What are the success criteria that will indicate that the
objectives have been met and the benefits delivered?
5.) Who is responsible for ensuring appropriate resources (time,
people and money) are allocated to improving your IT System?
6.) What is our budget and how much contingency will be
available in there for unexpected dilemmas?
7.) Are you open to acquiring new equipment/products that
could to facilitate a more advance IT System?
8.) What computer infrastructure do you currently utilize?
Hardware? Software?
9.) What type of software have you used in the past? MS Office
Products?
10.) What areas about your current IT system are your greatest
concerns? Current Processes
Sequence Use Case
Not the sequence use case is bare bones because of Club It’s
inferior IT system. They have a grossly undefined sequence for
ordering and inventorying. Since conventional keyboard input
systems is often impractical they rarely use the system. When
they do the ordering system can only print a
receipt.Requirements

9. List of Requirements There will be three dynamic and specific
system requirements that all interact with one another. They are
a Point-of-Sale System (POS), a Perpetual Inventory System,
and a SQL Database System.
POS System Process
· User inputs a request for order into any of the linked Kiosk
· A ticket is generated, printed, and logged for tracking
purposes
· Input order in automatically integrated into the Perpetual
Inventory
Perpetual Inventory System Process
· Orders automatically identified and sent into revolving
inventory tracking system have ingredients identified and
calculated against current inventory levels
· Unacceptable inventory levels are identified and an email
notification is sent out to pertinent personnel
· Predefined and prefilled order forms are automatically
generated and printed
SQL Database System Process
· Two separate databases titled Inventory Level and Sales; both
associated with POS and Perpetual Inventory System
· Authorized personnel can execute queries from predefined
utility script(s); query returns with pertinent data
· Reports can be printed or exported to email
[Club IT] CONFIDENTIAL PAGE 8