NFO620 Systems Analysis and Design:

Team Project Instructions

Matthew Manley, PhD, CISSP
Texas A&M University

August 4, 2015

Table of Contents
1.0 Introduction ...................................................................................................................................... 3
2.0 Team .................................................................................................................................................3
3.0 Requirements ....................................................................................................................................3
4.0 Deliverables ......................................................................................................................................3
4.1 Executive Summary ............................................................................................................... 4
5.0 Materials ...........................................................................................................................................4
6.0 Submission ....................................................................................................................................... 4
7.0 Grading .............................................................................................................................................4
Appendixes
Appendix A: System Specifications Document Template ...................................................................... 5
Appendix B: Grading Rubric ............................................................................................................ ........9

1.0 Introduction
The purpose of the team project is to provide an opportunity to apply systems analysis and design
knowledge to a specific business scenario. System requirements will be provided in the form of a
brief case description published on the course website. The resulting system specifications will
capture the business logic, data storage and interface design components of the final software
application using the object-oriented approach studied in class.
2.0 Team
Students are required to work in teams of three. If there are not enough students available
smaller teams may be formed with the instructor's approval. Team membership must be
communicated to the instructor verbally or by email at the commencement of the project (see course
syllabus for specific dates).
3.0 Requirements
In addition to addressing the user requirements specified in the business case description the software
application must adhere to the following general requirements.

The application must utilize a relational database management system (RDBMS).

The application must provide a graphical user interface.

4.0 Deliverables
Teams are required to submit the specifications for a new software application in a single document
that contains the following sections and/or figures:

Title Page
Table of Contents
Revision History
Executive Summary
System Specifications
Activity Diagram(s)
Requirements List and/or Description
Use Cases and Use Case Descriptions
Architecture Diagram(s)
Class Diagram(s)
Sequence Diagram(s)
Logical ER Diagram(s)
Other diagrams as team deems appropriate
Interface Mockup

Any assumptions related to ambiguous or missing requirements information may be incorporated

into the final system specifications document in a manner of the team's choosing. A template for the
final system specification document is presented in Appendix B.

4.1 Executive Summary

The Executive Summary section of the final system specifications document should present a brief
description of the underlying business case. More specifically, this section should include several
paragraphs (not to exceed two pages) that briefly describe who the system is for, what the purpose is,
and why it is necessary. Teams should carefully consider how to communicate the current state of the
system, the future state of the system and the measures required to close the gap, to the reader in a
concise yet thorough way.
5.0 Materials
Teams are free to use any word processing and diagramming software of their choosing as long as
they adhere to the fundamental symbols, shapes and/or notation presented in the text and class.
6.0 Submission
The final system specifications document shall be submitted in .pdf format via the course website, or
e-Campus, on the date specified by the instructor.
7.0 Grading
The possible points for each section of the final system specifications document are as follows.
Section
Title Page
Table of Contents
Revision History
Executive Summary
System Specifications (Content)
System Specifications (Composition)
Total Points

Points

25
100
25
150

Appendix A: System Specifications Document Template

(Comprising pages 5 through 8)

Name of Software
Version 1.0
ISYS620
Systems Analysis and Design
Team #1 Project

Table of Contents
1.0 Revision History ............................................................................................................................. 1
2.0 Executive Summary ........................................................................................................................ 2
3.0 Business Process Diagram .............................................................................................................. 3
4.0 System Specifications ..................................................................................................................... 4
[add appropriate subsections ]
5.0 Interface Mockup ............................................................................................................................ 8

Software Name

Page Number

1.0 Revision History

Number
1.0

Date
05/07/14

Changes
Initial Draft

Author(s)
Last Name, First Name,
Last Name, First Name,
Last Name, First Name

Appendix B: Grading Rubric

Category
Front Matter
(25 pts)

Excellent
All content presented
in organized and
clearly written form, i.e.
paragraph format
using provided
template.

Good
Content was
organized and clearly
written for the most
part. Ideas presented
were mostly clear.

Unsatisfactory
The organization and
writing made it
difficult to understand
who the authors were
and/or the underlying
business case for the
software.

Content
(100 pts)

All of the major

requirements were
addressed in depth.
Analysis and design
specifications were
well supported
by the
information
provided.

All of the major

requirements were
sufficiently addressed.
Analysis and design
specifications were
mostly supported by
the information
provided.

Major requirements
were insufficiently
addressed. Analysis
and design
specifications were not
supported by the
information provided.

Composition
(25 pts)

The diagrams were

well organized and
clearly presented. Any
writing was
grammatical and free
from errors.

The diagrams were

organized and clearly
presented for the most
part. Any writing was
mostly grammatical
and/or only a few
spelling errors were
present but they did
not hinder the
reader.

The diagrams lacked

overall organization.
The reader had to
make considerable
effort to understand
the system
specification.
Grammatical and
spelling errors made it
difficult for the reader to
interpret the text in
places.