Upload
sonam-patel-singh
View
8
Download
0
Tags:
Embed Size (px)
DESCRIPTION
IT
Citation preview
SCR -Training Information Management
System
Kaplan University
System Analysis & Design
Unit 10 Project
Tanya Day, Stephanie Faison, Kevin M. Harris,
Tammy Nikolova, Richard Rickard, Alma Williams
IT460-01AU
Unit 10: Systems Analysis and Design
2
Abstract
This document is a final assessment and recommendation for the SCR Training
Information Management System. The main objective of this paper is to provide a detailed plan
for the structure and implementation of the TIMS project. The information addressed will cover
the systems architecture including network topology, Web-centricity, scalability, and security.
The systems configuration will include a complete testing plan demonstrating support of its
reliability. The capacity planning will complete the range of requirements of this comprehensive
model supporting the SCR TIMS venture.
IT460-01AU
Unit 10: Systems Analysis and Design
3
Part 1. System architecture recommendations:
The best option for TIMS would be to implement client-server architecture because the
system will be fast and flexible. The application development will be object oriented and will
empower the user which in turn will improve productivity. The client-server architecture will
provide flexible processing options and allow IT professionals to share and configure the system.
Moreover, data can be distributed and placed closer to the user and that would be the best storage
option. A very flexible, multivendor model can be used for hardware and software integration. A
web server should be used for the system to allow Internet based communication between the
server and the clients.
To allow sharing of data and hardware resources, TIMS should join a WAN to connect
LANs, because when a user has access to data on a LAN or WAN, they see data as if it were
stored on their computer because the network is transparent. Distributed systems have great
capabilities because they can connect more than one LAN or WAN. A file sharing architecture is
recommended where the client handles:
o The user interface
o Sends data request to servers
o Receives data files from the server
o Runs application programs locally to process data
o Sends data files back to the server
The file server handles the following tasks:
o Receives data requests from the client
o Sends data files to the client
o Stores data files
IT460-01AU
Unit 10: Systems Analysis and Design
4
o Manages multiuser access
o Generates LAN traffic
o Manages data backup
A thin client design is recommended because most of the processing logic is located at the
server. The advantages of using a thin client include:
o Lower network traffic because most interaction between code and data takes place
at the server.
o Faster performance because less network traffic is required
o Lower initial cost because workstation hardware requirements are not as stringent
o Maintenance cost is lower because most program code resides on the central
server
The disadvantages of using a thin client design include:
o More difficult development because developers must optimize the division of processing
logic
IT460-01AU
Unit 10: Systems Analysis and Design
5
Client/Server Tiers:
A three tier design is recommended because it will allow the user interface on the client and data
can be stored on the server which can enhance overall performance by reducing the data server
workload.
LAN
Printer
Scanner
File
Server
Client
Client
Client
Data Application
Logic User
Interface
Data
Server
Applica
tion
Server
Client
Part 2. Detailed description and recommendations for architecture:
IT460-01AU
Unit 10: Systems Analysis and Design
6
The Business Dictionary defines legacy as Information stored in an old or obsolete
computer or format make it difficult to process or access. Legacy data is data that is difficult to
access and transport to a client/server environment. With the changes in technology, companies
need to keep up with competitors. If they are using software used when they initially started,
viewers / clients may have difficulty viewing or using the application. Migration is needed at
some point within an organization from older applications that follow open or standard
programming interfaces.
In order to get our legacy data to the new system we can perform data migration. Before
doing this we need to ask ourselves a few questions first:
Should we bring the data over to the new system?
Should we bring all or part of the data if we decide to migrate?
Which parts, if parts only?
Should certain data be filter in or out?
Is our data extractable?
Do we have someone in-house who can write the script to migrate data?
Will we hire someone if no one in-house can?
Will the task be performed manually?
When deciding on data migration, we need to take all factors into consideration before
we decide on moving the data to the new system (Infotechnet, 2009).
IT460-01AU
Unit 10: Systems Analysis and Design
7
If a decision has been made to migrate data, before moving can begin the following
analyses must be done:
Analyze and define source structure. Examine the structure of data in existing
system
Analyze and define target structure. Examine the structure of data in new system.
Perform field mapping. Mapping needs to be done between the existing and new
system.
Define the migration process. Will it be done manually or automate?
Consider the list of the system requirements including the inputs, outputs,
processes, performance and controls that SCR is looking in the new system.
o Outputs
TIMS must provide a master list of courses, students, and
instructors
TIMS should produce transcripts and verify records for former
students
TIMS could produce a class roster providing background
information about students
TIMS should generate registration and class roster printouts
Produce schedule printouts of all courses available for the next 90
days
Generate report on courses conducted and a listing of instructor
assignments
Report for SCR's corporate clients on their students
IT460-01AU
Unit 10: Systems Analysis and Design
8
Generate signature ready certificates with new logo for
successfully completing a course
o Inputs
TIMS must have future online form for students to input
registration information
Input screen should resemble systems used by other schools
Input schedule report for future reference to see which classes are
most popular
Input links to SCR Services: Systems Support Group,
Network/Web Group, Business Solutions Group, Project
Management Group
o Processes
TIMS must interact with the accounting system of SCR Associates
TIMS must have well organized Records
Send questionnaire to former and prospective students
System need to identify popular course offerings to estimate the
number of expected students
Accounting system should reconcile student accounts and bill
corporate clients for balances
Consolidate all SCR training in the new training group
o Performance
TIMS must be operational within six months
TIMS must support future online registration
IT460-01AU
Unit 10: Systems Analysis and Design
9
TIMS must track registration up to the day course is in session
TIMS must keep track of courses, instructors, scheduling,
registration, students, and grades
TIMS must track up-to-date industry certification requirements
TIMS should track credits earned toward IT industry certification
requirements
o Controls
Students must have pre-registered for course before joining a
training session
The system must have security for login screen
TIMS must have a minimum and maximum number of students for
courses open to the public
Grades should not be altered by students
Different levels of security should be provided to system
administrators than the students
SCR would like for the new TIMs (Training Information Management System)
system to be able to interact with the accounting system that is in place now.
IT460-01AU
Unit 10: Systems Analysis and Design
10
Centricity is defined as centering on or focusing on. It is usually used with another word.
Web centricity is an example of this and it means focusing on the web. Shelly Cashman
Rosenblatt defines web-centric as a strategy or approach that emphasizes a high degree of
integration with other Web-based components. A Web-centric architecture follows Internet
design protocols and allows a company to merge new applications into its e-commerce strategy
(2008).
SCR would like to offer online registration for courses that are available and keep track
of earned credits toward IT industry certification.
0
1
2
3
4
5
6
Inputs Outputs Process Control
TIMs
Scheduling Registration Records
IT460-01AU
Unit 10: Systems Analysis and Design
11
Part 3. Detailed description and recommendations for architecture:
The TIMS system requires architected Scalability, Security, and Batch processing.
These elements will provide the flexibility of a well balanced system providing longevity to
support the SCR-TIMS training objective for years to come.
The SCR-TIMS System Analysis team is designing the hardware and software to
accommodate scalability. Generally speaking this means that a system can be expanded,
modified, or downsized easily to meet the rapidly changing needs of the business enterprise. This
concept relative to the SCR-TIMS project is being looked at from more of a growth perspective
for expansion. The systems educations structure will be created with accommodations for
potential development opportunities in the areas of classes, staffing, and students. Our primary
focus will be in the areas of increasing support of the student base by developing class
opportunities to increased revenue.
The new network hardware will be easily integrated to the IT infrastructure by
connecting to an existing router attached to the legacy system. (See Figure below)
Network Infrastructure
IT460-01AU
Unit 10: Systems Analysis and Design
12
The new SCR-TIMS hardware is a Star Wired Network with a centralized network server
combined with a wireless router access point connected to a Web server. (See Figure below)
This design was chosen for many reasons. The primary reason for this network control
configuration was the ability to use multiple data storage locations and the unrestricted data flow
during batch processing of the classroom data stores to the TIMS dB. The classroom servers are
robust enough to handle multiple classrooms but for the sake of simplicity the diagram represents
one per class.
Figure of Integrated IT Star Network Structure
Classroom
Work Station 3
Staff Laptops
Remote Access
TIMS Training Center Network Layout
Legacy
System
Classroom
Work Station 2
Classroom
Work Station 1
Classroom
Work Station etc...
Web Server
Student
Remote Access
Network Server
Class Room Server 1 Class Room Server 3Class Room Server 2 Class Room Server 4
Class Room Server etc...
Wireless Router
TIMS dB
Router
Course
Data Store
Network Printer
Class Room Network
IT460-01AU
Unit 10: Systems Analysis and Design
13
The Wireless router and the Web server fit well with the need to be scalable in a volatile
market. There purpose is to create an environment for mobility. The wireless allows easy access
from anywhere on the facilities premises and the web server provides flexibility for remote
access. Both of these features are required to be competitive in todays educational market.
Batch processing is data collected in a location processed and transferred in groups to
another location. In the TIMS case the data is stored on a class room dB until it is time to transfer
the data. The course data storage process is to minimize data transfer during peak hours of the
day. This is what was referred to in the prior paragraph as TIMS Batch processing. The
course/student information is saved on a local database during the day. The transfer is directed
by the classroom server at a set point in time when network traffic is minimal through the
network server to the primary TIMS database. (See Figure below) There is a level of control that
will be implemented during batch processing. To promote data accuracy and quality during this
process a log file will be produced to capture all elements that have been transferred to TIMS.
This also reduces direct access to TIMS eliminating security exposures.
Classroom
Workststion
Course
Student
Information
TIMS Batch Processing Flow
Information
Collect Program
Daily
Info-Collection
Program
Reports
Certificates
Generated
Course Student
Information file
TIMS Course
Student
Information
Figure of Batch Processing Flowchart
IT460-01AU
Unit 10: Systems Analysis and Design
14
SCR-TIMS IT security management is universally an issue that will be addressed in hardware,
software, and procedural controls to safeguard and protect this system and its data from internal
and external threats. All of the growth requirements have been carefully planned with security
measures present. Our design will provide measures to detect intrusions and provide stringent
rules for passwords and user identification. The TIMS system will be integrated with the legacy
security features of the existing system.
Hardware Physical Security Management: This function entails the physical security
of assets protecting them from being stolen or tampered with.
All the servers will be housed in Computer rooms with secure card reader with
personal identification access points. Emergency access will be alarmed to maintain the
integrity of each computer room.
The Network Backbone infrastructure will be secured with physical separation in
IT closet located in each servers computer room.
The desktop computers will be physically secured to each classroom desk to
prohibit the units being stolen.
Notebook computers will primarily be used by staff and this is our most
vulnerable asset to manage. While being used on site staff will be responsible to cable
lock each unit to a secure point in their office or cubical.
IT460-01AU
Unit 10: Systems Analysis and Design
15
Network Security Management: This is the fundamental premise for the SCR-TIMWS
system. Devices connected together transmitting and receiving data between each other.
Network security issues stem from the need to protect personal information from
deviant individuals. Information transmitted without the proper protection remains
vulnerable to unwarranted attacks.
SCRs reasoning for Encrypting network traffic is to reduce the exposure for
intercepted transmissions. An intercepted transmission if encryption is implemented
causes the contents to be masked versus plain text which can be easily read and stolen.
We have potential for sensitive personal information being transmitted including
passwords.
We will be using Public key encryption on our wired network which will provide
the masked protection required if someone has the luck to infiltrate our system network.
This is a bit more secure than our wireless network because it resides behind the systems
firewalls.
TIMS wireless network will be using the highest level of Wi-Fi Protected Access
(WPA2) available. This Temporal Key Integrity Protocol (TKIP) uses a stronger
encryption. This is done by creating a new encryption key for each session creating
variability the standard. This minimizes anyone being able to crack the encryption
methodology being used.
SCR will not incorporate a private network due to the cost associated with the
hardware contingency of a private network line. We will be tunneling by use of a virtual
private network using the encryption techniques available.
IT460-01AU
Unit 10: Systems Analysis and Design
16
SCR will have a unique port assigned to connect its services. This port will be
undetectable with SCRs use of routers in series to the external network providing a
hardware firewall. The routers provide network protection by using network address
translation (NAT) this works in conjunction with the Ethernet protocol TCP/IP. The
transmissions originating from the SCR-TIMS systems TCP/IP address will be
translated by the router into requests from its single IP address on the WAN or Internet
side of the router. (See Figure below)
Internet
Web Server
Router
IP 28.2.324.4
IP 12.0.0.4
IP 12.0.0.3
Classroom
Work Station 2
Classroom
Work Station 1
Figure illustrating simplified concept of network Router Firewall protection
Software Application Security Management: These will be handled by the user group
access levels.
Application security will be handled by the system analyst related to
configuration and functions. Understanding these services will help identify security
concerns.
Services are a necessary part of network communication. These can be breached
if not monitored and controlled. This will be handled by user rights associated with their
account access level.
IT460-01AU
Unit 10: Systems Analysis and Design
17
Input validation will be handled at the user interface designed in to the database
system. These data controls will be done to promote and ensure integrity of the data as it
is input into the system. This is to accommodate fast changing processes, personnel
turnover and new incoming students. This will also reduce security exposures. Therefore
system managers have to take ownership of making the system 'Idiot-resistant', if not
'Idiot-proof'.
Patches and updates to each work station will be downloaded and require user
intervention to install and activate.
Database File Security Management:
There will be Backup and recovery policies and procedures to protect data stored
in TIMS protect this information from damage or loss. If by remote chance something
happens and the integrity has been compromised we will have the ability to restore and
recover lost or damaged data.
File Security is defined by personal or sensitive data that is stored in files on the
server or database. It is a vital part of every data storage system. SCR will handle this for
the TIMS project by defining user groups and assigning permissions. This is a
requirement of the system because the clients/staff will be using/sharing applications and
files.
The User groups will be defined and consist of system administrators, managers,
and clients. Basically three levels of access. These levels will allow certain privileges and
be controlled by the rank in group permissions.
Permissions will stem between read, write, and execute broken down into access
and ability to perform file/application manipulation. The categories are as follows.
IT460-01AU
Unit 10: Systems Analysis and Design
18
Read a file read file contents only
Write a file store files change file contents
Execute a file run available programs
Read a directory view contents of directories
Write a directory add/remove contents of directories
User Access Security Management: User security issues will be handled with
procedural controls managed by the site system administrators with respect to user
facility access levels based on their requirements.
Site Identity management will be handled by displaying ID cards on each person
from students and staff. A color coded stripe will be located on each ID designating the
hierarchy for ease of identification.
Password protection will be maintained at various levels. All systems from
servers, classroom PC to notebooks will be required to maintain hard drive or bios level
password protection and system user password protection all being monitored and
reported daily by SCRs work station security tools. These passwords will require 8
digits, 8 rotational password changes, and not repeatable character password changes.
This process minimizes the ability for deviant to breach access to the system.
Social engineering is a deviant attempt gain system access. These attempts would
be through various means of social interaction friendship and misrepresentation of their
affiliation. This will be handling by SCR as an introductory administrative educational
package that all clients and staff will have to take prior to any level of system access. The
staff will be on a yearly review process to eliminate exposures due to complacency.
IT460-01AU
Unit 10: Systems Analysis and Design
19
The executive level at SCR may provide the highest level of user resistance adhering to
security guidelines related to system passwords and various other security measures. In order to
be connected all system users will be required to use the Workstation security application. As
stated before this tool will monitor and report any violations to the system administrator.
Part 4. Design specification:
The system design specification will contain a full system design. It will also include a
detailed plan for the actual implementation of the system. A document with the systems design
specification will include detailed costs, staffing, and scheduling for the implementation will also
be contained herein, with supporting charts and diagrams.
This specification will be what the operational system is measured against. This
document is designed for programmers who will be creating the actual system itself. Approval
of the system will need to come from throughout the design process, and it will come from those
within the I.T. department and other stakeholders for this project. They will approve the design
and functionality of the areas of the system that directly affect them.
At the end of the system design phase, multiple presentations will be made to explain the
system and answer any questions. Comments made during these sessions will be considered, and
final approval will be sought for the system, with the final presentation being with management.
If approved, the implementation of the system will proceed. The following can be included in a
complete Table of Contents for this system design specification: Cover Page, Executive
Summary, System Components, System Environment, Implementation Requirements, Time and
Cost Estimates, Appendices and Index.
IT460-01AU
Unit 10: Systems Analysis and Design
20
Part 5. Design specification (Please double click the Table of Contents to launch document:
System Design Specifications for SCR-TIMS
Table of Contents
1. Executive Summary ................................................................................................................................ 2
2. System Components ............................................................................................................................... 3
2.1 User Interface ................................................................................................................................ 3
2.2 System Requirements .................................................................................................................. 11
3. System Environment ............................................................................................................................ 14
3.1 Architecture ................................................................................................................................. 14
2.1 Hardware ..................................................................................................................................... 16
2.2 System Software ......................................................................................................................... 21
4. Implementation Requirements .............................................................................................................. 24
3.1 Capacity ...................................................................................................................................... 24
3.2 User Training Requirements ....................................................................................................... 25
3.3 Test Plans .................................................................................................................................... 25
3.3.1 Types of Testing ...................................................................................................................... 25
3.3.2 Roles and Responsibilities ...................................................................................................... 28
3.3.3 Assumptions for Test Execution ............................................................................................. 29
3.3.4 Constraints for Test Execution ................................................................................................ 30
5. Cost Estimates ...................................................................................................................................... 30
6. INDEX .................................................................................................................................................. 33
IT460-01AU
Unit 10: Systems Analysis and Design
21
Part 6. Testing plan:
Your new system will be thoroughly tested. For the majority of testing, there will be a
small test bed consisting of 7 machines. Of these 7 machines, there will be one machine to
represent the Executive, Systems, Project Management, Business Solutions, Network/Web,
Business Solutions, and Administrative groups. There will also be one machine that will reflect
those of the Training center. Each machine is connected to the server and have the settings,
permissions and programs specific to that group and is tested for compatibility. Prior to testing, a
test plan is created and all test cases are documented. Documentation for users, managers and IT
are created before testing and edited during testing. There are 4 major testing methods that will
be used.
Unit Testing:
Unit testing is a software development process in which the smallest testable parts of an
application or network, called units, are individually and independently examined for correct
function. The purpose of the Unit Test is to recognize and eliminate execution that could have
been missed during desk checking.
For this section of testing, we will use test data that will include correct data and
erroneous data. Testing with the correct data is called positive testing and testing with the
negative data is called negative testing. Both methods are equally as important to make sure that
the program functions properly when it is used correctly and incorrectly.
Here each part of the network will be tested separately. First we will test the server. The
operating system and all of the individual software pieces will be checked to make sure that they
are compatible. This will be done by verifying all of the functionality of the services, the
IT460-01AU
Unit 10: Systems Analysis and Design
22
operating system and any other program that is housed on the server. The disk array and router
will then be checked for functionality.
We will then set up each of the 7 computers for the test bed. Each of these computers
will be tested to verify that the software on the machine works while the machine is used as a
standalone machine. The server, the printer, the hardware of tier 2 and tier 3 are tested
separately to make sure that all parts work. Its then demonstrated that all the legacy data can be
imported into the new programs and that those programs work effectively.
Integration Testing:
Testing two or more programs that depend on each other is called integration testing.
(Rosenblatt 2008). In Integration Testing components of the system are combined and tested in
different ways. When you have programs and components of the network that depend on each
other to perform a function then it is imperative to make sure that they work together correctly.
Again in this phase of testing we will use both positive testing that simulates your actual
conditions and negative testing that simulates incorrect conditions. There are 2 types of
integration testing methods: bottom-up and top-down. Bottom-up begins with the simplest parts
of the network and then moves up to the server. Top down testing is just the opposite. We are
using a top down method since we are starting with the server.
During the integration testing phase we will verify that all of the hardware functions
together. This is the time that computers will be connected to network. We will verify that there
isnt any issue sending updates between the server and the client machines. We will verify that
the client machines can connect to the server. It is also verified during this time that the
permissions for each of the user groups are functioning as they should. It is verified that all
IT460-01AU
Unit 10: Systems Analysis and Design
23
computers can print to the printers on the network and the other devices on the network such as
scanners communicate with the computers on the network and vice versa.
During the integration testing phase we will ensure that programs that work together
without issue. We will verify that things like your anti-virus and firewall arent causing conflict
with any of the programs on the client machine.
System Testing:
System testing is where the entire system will be tested for functionality. This is a final
testing of all programs and the network. In this final testing we will make sure that they system
can handle the predicted volumes of data quickly and efficiently. We will make sure at this time
all of your IT staff is trained on the new system and prepared for your Go-Live. All
documentation for the users, managers and IT staff is finalized to include changes found during
testing, and dispersed this time. Since we have been working with a test bed up until this point,
we will now get a small group of 7 beta users set up on the new network. The beta group will be
1 person from each of the 7 groups. They will be given the machines used in the testing phase.
They will use the system as they normally would in their daily roles. This way we can get actual
daily activity on the system to test everything. It is in this phase that any scenarios that werent
caught in the earlier phases testing will be caught and we can ensure that any possible problems
are corrected prior to your go-live. The beta team will perform the acceptance test.
Acceptance Testing:
Acceptance Testing is the final phase of testing. Acceptance testing completes the formal
testing process and is the only test that is the responsibility of the customer. (TechRepublic 2009)
In this step a group representing a cross section of end users tests the application. In your case it
would be the beta group that we established during system testing. The user acceptance testing
IT460-01AU
Unit 10: Systems Analysis and Design
24
is done using real world scenarios and perceptions relevant to the end users. Acceptance testing
is where users test the system before accepting it. The user will execute the test cases that
they have prepared and use the system in their day to day routine.
Upon successful completion of the User Acceptance Testing and resolution of the issues
the team generally indicates the acceptance of the system. If it isnt accepted, we will work with
the users to get the system to their liking so that everything is happy and a sign-off can occur.
After the system has been accepted, it will be rolled out to all of the other users. (Exforsys 2009)
Part 7. Testing plan:
This is the Master Test Plan for the SCR-TIMS project. This plan will address only those
items and elements that are related to the SCR-TIMS network, both directly and indirectly
affected elements will be addressed. This test plan will define testing strategies for each area
and sub-area to include all the functional and quality requirements. The design specifications
will be divided into testable areas. The plan will also define bug-tracking procedures. Risk will
be identified in detail. This test plan will identify required resources and provide a testing
schedule.
The project will have 4 levels of testing: Unit, Integration, System and Acceptance. The
details for each level are addressed in the approach section.
TEST ITEMS
The following is a list of the items to be tested:
Server machine
Disk Arrays
IT460-01AU
Unit 10: Systems Analysis and Design
25
Network Communication
Client machines. This includes all software on the machine. This will be done by
groups.
Executive
Systems
Project Management
Business Solutions Network/Web
Business Solutions
Administrative
Printers
Faxes
Scanners
Firewall
RISK ISSUES
Server updates and access.
The operating system updates. We have no way of testing to see if future updates
will cause issues with the system.
IT460-01AU
Unit 10: Systems Analysis and Design
26
Backup and Recovery and local databases must be carefully checked to make sure
there isnt any conflict.
Legacy data could be corrupt or may not import properly.
Network security must be defined and verified. Since there will be much
communication between components on the network we must make sure that
everything has access.
APPROACH
Unit Testing
Technical design has been completed and approved
Test data
Extensive testing on clients machines
Verify all Legacy data can be imported
Test Hardware
Servers
Printers
Routers
Integration Testing
Test Program or Programs
Testing Schedule
Test scripts
IT460-01AU
Unit 10: Systems Analysis and Design
27
Issues and defects documented
Network Communication (client can communicate with server and also that server
can communicate with the client)
Verify Printers
Send Faxes
Updates from server
System Testing
Unit testing of each module.
Schedule is made and in place for System Testing
Tracking plan has been approved
Testing environment established
Acceptance Testing
Test functionality and usability
Design user acceptance case tests
Execute test environment
Document defects found
Resolve issues
User sign off
Meetings
The test team will meet once every two weeks to evaluate progress to date and to identify
error trends and problems as early as possible. The test team leader will meet with the project
IT460-01AU
Unit 10: Systems Analysis and Design
28
manager once every two weeks as well. These two meetings will be scheduled on different
weeks. Additional meetings can be called as required for emergency situations.
Measures and Metrics
The following information will be collected by the QA team during the Unit testing
process. This information will be provided to network admin as well as provided to the project
team on a biweekly basis:
Defects by area and severity.
Defect Origin
Time spent on defect resolution by defect, for Critical & Major only. All Minor
defects can be totaled together.
TEST DELIVERABLES
Acceptance test plan
System/Integration test plan
Unit test plans/turnover documentation
Screen prototypes
Report mock-ups
Defect/Incident reports and summaries
Test logs and turnover reports
(Toolbox.com, 1998-2009)
IT460-01AU
Unit 10: Systems Analysis and Design
29
REMAINING TEST TASKS
TASK Assigned To Status
Create
Acceptance Test
Plan
TM, PM, Client
Create
System/Integration
Test Plan
TM, PM, Dev.
Define Unit
Test rules and
Procedures
TM, PM, Dev.
Define
Turnover
procedures for each
level
TM, Dev
Verify
prototypes of
Screens
Dev, Client, TM
Verify
prototypes of
Reports
Dev, Client, TM
(Toolbox.com, 1998-2009)
IT460-01AU
Unit 10: Systems Analysis and Design
30
ENVIRONMENTAL NEEDS
The following elements are required to support the overall testing effort at all levels
within the TIMs project:
TIMs System Group
A SCR staff member will participate in the software or solution development activities.
Responsibilities:
Develop the system/application
Develop cases and requirements in collaboration with TIMs Adopters
Conduct Unit, System, and Integration testing
Support user acceptance testing
TIMs Adopter
This will include an SCR project manager and a member of the TIMs System Group to
forego formal adoption, testing, validation, and application of products or solutions developed by
Workspace Developers. Responsibilities:
Contribute to Use case, requirement development through review
Contribute to develop and execution of the development test scripts through review
Conduct Full User Acceptance, regression, and end-to-end testing; this will include
identifying testing scenarios, building the test scripts, executing scripts and reporting
test results
IT460-01AU
Unit 10: Systems Analysis and Design
31
TIMs Testing Process Management Team
This group will include SCR Leads that are allocated to the TIMs system. The Group
responsible to manage the entire testing process, workflow and quality management with
activities and responsibilities to:
Monitor and manage testing integrity
Support testing activities
Coordinate activities
Assumptions for Test Execution
For User Acceptance testing, the TIMs System Group has completed unit,
system and integration testing and met all the Requirements (including
quality requirements) based on Requirement Traceability Matrix.
User Acceptance testing will be conducted by End-users
Test results will be reported on daily. Failed scripts and defect list will be sent
directly to developers.
Constraints for Test Execution
TIMs Adopters should clearly understand test procedures and record a defect
or enhancement. Testing Process Team will schedule a meeting with TIM
System Group and TIMs Adopters to address any testing related issues.
TIMs System Group will receive a list of request for the test environment set
up, user accounts set up, data set, and defects list.
IT460-01AU
Unit 10: Systems Analysis and Design
32
TIMs System Group will support ongoing testing activities based on priorities
Enhancement can be added as new requirement after the appropriate Change Management
process. Documentation for all steps in the testing needs to be completed:
To all IT stall,
Please remember to complete documentation. It is important to document all the steps during
testing.
Team D
Part 8. Capacity planning:
Whenever you develop a new program or system, one of the most important things to
consider is future growth. If youre application can only support 30 users at a time, what will
happen when your user base is 120? While it cannot complete eliminate future capacity issues,
capacity planning is a vital element in the systems development process.
Capacity planning is simply estimating the amount of technology resources, whether
hardware, software, or infrastructure, that will be needed over a certain period of time. This
information is vital as it can help a company plan for future technology purchases in their
budgets. The key to good capacity planning is to have new resources available for use as soon as
they are needed, as opposed to sitting idle for long period s of time.
There are certainly benefits and drawbacks to doing capacity planning. The benefits are
that you plan ahead for future growth and rarely are caught off guard and have to make rush
purchases for new equipment. It also allows you to plot out upgrades, again to avoid rushes that
cause system outages during heavy volume hours. The downside is that if the growth is not
there, purchased resources lay idle wasting money and space.
IT460-01AU
Unit 10: Systems Analysis and Design
33
As it relates to the TIMS project, I think capacity planning is absolutely vital to the
ongoing success of this system. I would certainly recommend using an open source planning
tool, such as Hyperic HQ, to accomplish this task. I would also recommend that the systems
analyst spearhead this effort, with input from those who played a significant role in the
development of TIMS.
Conclusion
The final recommendation for the SCR Training Information Management
System designs, architecture and scalability should embrace future growth. A detailed plan for
the structure and implementation of the TIMS project has been presented covering network
topology, Web-centricity, testing and security.
IT460-01AU
Unit 10: Systems Analysis and Design
34
References
Bentley, J. E. (n.d.). Planning, Development and Support: Software Testing Fundamentals
Concepts, Roles, and Terminology. Retrieved December 17, 2009, from S.A.S:
http://www2.sas.com/proceedings/sugi30/141-30.pdf
Borysowich, C. (2005, February 24). Testing: A Sample Test Plan . Retrieved December 17,
2009, from Toolbox for IT: http://it.toolbox.com/blogs/enterprise-solutions/testing-a-
sample-test-plan-3283
BusinessDictionary.com. (2009). Legacy Data. Retrieved December 17, 2009, from Business
Dictionary: http://www.businessdictionary.com/definition/legacy-data.html
caBIG. (2008, September). Test Plan Template Baseline. Retrieved December 17, 2009, from
cancer Biomedical Informatics Grid: cabig.nci.nih.gov/.../Test Plan
Template_Baseline.doc
Capacity Planning. (2009). Hyper HQ official website. Retrieved December 17, 2009 from
http://www.hyperic.com/products/capacity-planning.html
Capacity Planning. (2009). Tech Target. Retrieved December 17, 2009 from
http://searchenterprisewan.techtarget.com/sDefinition/0,,sid200_gci1082579,00.html
Cashman, T.J., Rosenblatt, H.K., Shelly, G.B. (2008). Systems Analysis and Design (Seventh
Ed.). Boston, Massachusetts: Course Technology, Cengage Learning
Computerworld Inc. (2006, August 24). How to Set Up WPA2 on Your Wireless Network .
Retrieved December 17, 2009, from Computerworld:
http://www.computerworld.com/s/article/9002706/Tutorial_How_to_set_up_WPA2_on_
your_wireless_network_
IT460-01AU
Unit 10: Systems Analysis and Design
35
Course Technology, CENGAGE Learning (2008). Network+ Guide to Networks (4th ed.).
Boston, Massachusetts: Course Technology, CENGAGE Learning.
Exforsys.com. (2000 - 2009). What is User Acceptance Testing? Retrieved December 17, 2009,
from Exforsys Execution for Systems: http://www.exforsys.com/tutorials/testing/what-is-
user-acceptance-testing.html
Gerrard Consulting. (2009). TEST PLAN OUTLINE. Retrieved December 17, 2009, from
Gerrard Consulting :
http://www.gerrardconsulting.com/tkb/guidelines/ieee829/example.html
InfoTechNet. (n.p.). DATA MIGRATION. Retrieved December 17, 2009, from Infotechnet:
http://www.infotechnet.org/ntca/DataMigration.htm
Japenga, R. (2008). How to Write a Great Software Test Plan. Retrieved December 17, 2009,
from Microtoolsinc: http://www.microtoolsinc.com/howstp.php
Johnson, R. (2008). Performance Monitoring and Capacity Planning. IT World. Retrieved
December 17, 2009 from http://www.itworld.com/swol-1195-unix?page=0%2C0
Microsoft Corporation. (2009). Chapter 16 - MS Network Client Version 3.0 for MS-DOS.
Retrieved 2009 17, December, from Microsoft:
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-
us/net/net4dos.mspx?mfr=true
Migration Solutions Ltd. (n.p.). Data Centre & Computer Room Security. Retrieved December
17, 2009, from Migration Solutions: Migration Solutions:
http://www.migrationsolutions.com/computerroomsecurity
IT460-01AU
Unit 10: Systems Analysis and Design
36
Mochal, T. (2001, October 22). Acceptance testing: The customer is the ultimate judge.
Retrieved December 17, 2009, from Techrepublic:
http://articles.techrepublic.com.com/5100-10878_11-1044625.html
National Center for Biotechnology Information. (2003, revised August 21). National Center for
Biotechnology. Retrieved December 17, 2009, from Network Client/Server Applications:
http://www.ncbi.nlm.nih.gov/Web/Search/client.html
Series, S. C. (2008). A JAD Session Example. Retrieved from SCR Associates:
http://oc.course.com/sc/sad7e/scr/intranet/jadsession.cfm
TechTarget . (n.p.). Plotting and Presenting. Retrieved December 17, 2009, from Tech Target
Events:
http://media.techtarget.com/searchSoftwareQuality/downloads/Mging_the_Testing_Proce
ssCh2.pdf
TechTarget. (2006 - 2009). Bottom Up Approach to Network Troubleshooting. Retrieved
December 17, 2009, from TechTarget Events:
http://searchnetworking.techtarget.com/tip/1,289483,sid7_gci950291,00.html#
TechTarget. (2006 - 2009). Integration Testing. Retrieved December 17, 2009, from TechTarget
Events:
http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci1243430,00.html
TechTarget. (2006 - 2009). Unit Testing. Retrieved December 17, 2009, from TechTarget
Events:
http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci1243425,00.html
Wikimedia Foundation, Inc. (2009, modified December 6). Client-server. Retrieved December
17, 2009, from Wikipedia: http://en.wikipedia.org/wiki/Client-server
IT460-01AU
Unit 10: Systems Analysis and Design
37
INDEX
Bugs Any error or defect that causes the software, application or hardware
to malfunction.
Enhancements Any alteration or modification to the existing system for better
workflow and process.
2) An error or defect that can cause the software, application or
hardware to malfunction.
Where 1) and 2) is NOT included in the requirements can be
categorized as an enhancement. Pg 32
.
IT460-01AU
Unit 10: Systems Analysis and Design
38
Project Responsibilities:
Tammy Nikolova (1), Tanya Day (2, 7), Kevin Harris (3),
Richard Rickard (4, 8), Stephanie Faison (5+ main doc), Alma Williams (6),