Running Head: GROUP B PRE-REVIEW
Group B: Pre-Review
Final Project
IT460 Systems Analysis and Design
Henk Robinson
1
GROUP B PRE-REVIEW
2
TIMS System’s Architecture
TIMS
Internet
Router
Firewall
Corporate
Server
Proposed Network
Executive
Group
Business
Solutions
Group
Master
Authentication
Server
Core
Switch
Administrative
Support
Group
Web
Server
User
Switch
Database
Application
Server
Database
Server
Network Design:
Star Topology
Data
3 Tier Database
Design
Systems
Group
Project
Management
Group
Network
Web
Group
AS400
Training
Group
Data
Disk
Array
GROUP B PRE-REVIEW
3
Detailed Description and Recommendations for TIMS Architecture
The proposed Training Information Management System (TIMS) training center will be a
portal based distance learning system that will allow us to meet the needs of more potential
students and corporate clients interested in the furthering their training in computer hardware and
software. Moreover, without the added expense of setting up facilities in other locations, we will
be able to fund a new web-based infrastructure so that students and clients will be able to access
training through our web server. We will continue using the corporate server for email and
file/print services, and by converting the legacy AS400 to use TCP/IP we will still be able to
connect to it. We will be adding a master authentication server to control access to the network,
and we have decided on a 3 tier database design with the database server separate from the
application server to improve performance and grant more flexibility between client/server
applications. The web server will have a ‘web centric’ interface that allows students and clients
to use the internet to talk to our web server and access certain data from our database for training
purposes. Active Directory will be utilized to create user groups that will restrict access to
network by defined policies.
Scalability: Security and Batch Processing
Scalability
The new TIMS System will have the ability to handle increased business volume and
transactions in the future based on the researched study of the inputs, outputs, and processes. For
example, if we consider In-House Development of the TIMS project, we already know an
approximation of what the future volume will be and all the inputs, outputs, and processes. So,
from this information we know approximately the maximum number of concurrent users of the
system and the approximate peak times. Furthermore, with our three year worksheet/four year
GROUP B PRE-REVIEW
4
estimations we can make sound future hardware and volume projections. Another point to
mention here is with realistic volume projections, we can provide reliable cost estimates for
related expenses.
Security
As far as security is concerned the TIMS project will be secured in all six levels of
system security which consist of the: physical, network, application, procedural, file, and user
security. What we will do is make sure that our server rooms are locked to all unauthorized
personnel by providing special protection. All access points will have internal hinges and
electromagnetic locks that are equipped with a battery backup system to provide standby power
in the event of a power outage. Moreover, security authentication mechanisms will provide:
biometric scanning system (which will map any personnel in the server rooms), video cameras,
and motion sensors. The network security will use public key encryption, virtual private network
(VPN), Firewalls, and a network intrusion detection system (NIDS) to secure the network.
Application security will be used to protect all server-based applications. Procedural, file, and
user security will be secured by using: backups and paper shredding, permissions, identity
management, and password protection. All of these security procedures will be used to secure the
new TIMS project.
Batch Processing
For data that is processed in groups like our reports, end of semester grades, student
registration, and scheduling, we will use batch processing. What this will afford us is the use of
batch processing characteristics which are: collecting, grouping, and processing transactions
periodically which can be run on a predetermined schedule without user involvement at times
when the system is not using many resources.
GROUP B PRE-REVIEW
5
Design Specifications: Detailed Explanation of TIMS Design Specifications
Detailed Explanation of TIMS Design Specifications
A detailed explanation of the TIMS design specifications started in the systems analysis
phase with a data flow diagram (DFD) which uses various symbols to show how the system
transforms input data into useful information. We decided to use Gane and Sarson symbol set
and started with a context diagram. The context diagram for the TIMS project provided a top
level view of an information system that shows the system’s boundaries and scope. Our context
diagram consisted of six entities and one central process 0 (TIMS 0) which represents the entire
information system. We proceeded from the context diagram to create a 0 DFD which zooms in
on the system and shows major internal processes, data flows, and data stores. What Diagram 0
also displays is a repeat of the entities and data flows that appeared in the context diagram. From
here we opened the system one more step and created a 1 DFD that allowed us the ability to
explode, partition, and decompose the system even further. The detailed DFDs are displayed in
the next section.
GROUP B PRE-REVIEW
Design Specifications Diagrams of TIMS Implementation
Context Diagram
6
GROUP B PRE-REVIEW
0 DFD
7
GROUP B PRE-REVIEW
1 DFD
8
GROUP B PRE-REVIEW
Entity Relationship Diagram (ERD)
9
GROUP B PRE-REVIEW
Structured Chart
10
GROUP B PRE-REVIEW
11
Development of Testing Plan
1. Initial Compilation of Code
1.1. Syntax errors: Language grammar errors that keep program from running
properly.
1.2. Code review: a type of desk check that looks for logic errors that keep program
from executing properly.
1.3. Design walkthrough: a review with a cross section of end users to verify all
features were included.
2. Unit testing
2.1. Design valid and invalid test data that will simulate all possible results.
2.2. Decide who will participate in the testing.
2.3. Review results of testing.
2.3.1. Cycle back through steps as needed until program clears testing.
3. Integration testing (verify works well with other programs)
3.1. Design data that will simulate actual data that can be passed between programs,
including erroneous data.
3.2. Decide who will participate in testing.
3.3. Review results of testing.
3.3.1. Cycle back through steps as needed until program clears testing.
4. System Testing
4.1. Perform final test of all programs.
4.1.1. Verify system will handle all input data properly, both valid and invalid
data.
GROUP B PRE-REVIEW
12
4.2. Documentation and Instructions
4.2.1. Verify IT staff has operational documentation and instructions needed to
properly operate system.
4.2.2. Backup and restart capabilities of system are adequate.
4.3. Verify all system components are integrated properly and that actual processing
situations will be handled correctly.
4.4. Confirm that the information system can handle predicted volumes of data in a
timely and efficient manner.
5. Operation testing
5.1. Decide how the system will be implemented.
5.1.1. Parallel operation: changeover with both old and new running at the same
time, checking results of new against old, eventually terminating the old
system.
5.1.2. Pilot operation: changeover implementing new system at a selected
location, the pilot site is actually run as a parallel operation so you have a
system check between old and new.
5.1.3. Phased Operation: implementing new system in stages.
5.2. Post Implementation Evaluation.
5.2.1. Review of system after a set time frame.
5.2.2. Decide if any changes or modifications that may be needed.
5.3. Sign off of new system.
GROUP B PRE-REVIEW
13
Testing Plan Implementation
Testing Stage
System Analyst
Programmers
1.1 Syntax Errors
X
1.2 Code Review
X
Users
1.3 Design Walkthrough
X
X
2.1 Design Unit Test Data
X
X
2.2 Unit Testing
X
X
X
2.3 Unit Test Review
X
X
X
3.1 Design Integration Test Data
X
X
3.2 Integration Testing
X
X
X
3.3 Integration Test Review
X
X
X
4.1 Final System Test
X
X
X
4.2 Documentation and Instructions
X
X
4.3 Verify System Integration
X
4.4 Data Volume Check
X
5.1 Implementation
X
X
5.2 Post Evaluation
X
X
Capacity Planning
Capacity Planning
Since capacity planning involves monitoring current activities and performance
levels, anticipating future activities, and forecasting the resources needed to provide
desired levels of service, the first step in the capacity planning process would be to
create a working model based on the system’s present workload and performance.
X
GROUP B PRE-REVIEW
14
Then we would use the projections from our three year worksheet to make a series of
what-if analysis to vary one or more elements in the model. What this will ultimately
afford is multiple models so that we can measure the effects model against model. The
what-if analysis can be accomplished by using Microsoft Excel.