1. Kaplan University IT460 System Analysis & Design
Unit 8 Seminar

2. Unit 8 Objectives Due this week Chapter 10 – System Architecture
Chapter 11 – Managing Systems Implementation
Final Project
Tonight we are going to get to know each other and review the syllabus which covers the course expectations and what we can expect of each other as well as a brief review of where to find everything in our classroom.

3. Unit 8
Due by Tuesday, February 29

4. Due by Tuesday, February 29
For Unit 8:
Read Chapter 10 – System Architecture
Read Chapter 11 – Managing Systems Implementation
Complete the two Discussion Questions
Complete both parts of the assignment
Continue work on Final Project

5. Unit 8: Discussion Questions
Systems Architecture is a topic that addresses many technologies. In this thread please select one or more of these technologies, investigate what issues must be addressed by Systems Analysts and then share your plan with our classmates.
What are the issues we face in the Systems Implementation Phase?

6. Unit 8 Assignment (Part A)
Part A: ERP Solutions
Jesse wants you to recommend a vendor who offers an ERP strategy.
You need to review the SAP and Oracle Web sites, and at least two others that offer ERP solutions.
Reply to her with the results and the reasons for your recommendations.
SCR-TIMS Work Sessions Session 10 To Do List #1

7. Unit 8 Assignment (Part B)
Part B: Structure Chart
Jesse wants to see a structure chart.
She said to use program modules based on the processes we identified earlier.
She wants the modules to be cohesive and loosely coupled.
SCR-TIMS Work Sessions Session 11 To Do List #1

8. Grading Rubric for Assignment
15 pts – Review SAP and Oracle websites
15 pts – Review 2 other vendors for ERP solutions
10 pts – Provide a structure chart based on the processes and modules described in previous units

9. Chapter 10
System Architecture

10. Introduction
System architecture translates the logical design of an information system into a physical structure that includes hardware, software, network support, and processing methods

11. System Architecture Checklist
Enterprise Resource Planning (ERP)
The objective of ERP is to establish a company-wide strategy for using IT resources
Supply chain management (SCM)

12. System Architecture Checklist
Scalability
Scalability, also called extensibility, refers to a system’s ability to expand, change or downsize easily to meet the changing need of a business enterprise
Especially important in implementing systems that are volume-rated, such as transaction processing systems

13. System Architecture Checklist
Web Integration
An information system includes applications
Web-centric architecture
Avoids many of the connectivity and compatibility problems that typically arise
E-marketplaces

14. System Architecture Checklist
Legacy System Interface Requirements
The new system might have to interface with one or more legacy systems
Interfacing a new system with a legacy system involves analysis of data formats and compatibility
The analyst must know if the new application eventually will replace the legacy system

15. Legacy Considerations
For the TIMS System, what legacy data should be considered?

16. System Architecture Checklist
Security Issues
Name several security issues with TIMS System.

17. Planning the Architecture
Servers
Server
Clients
Mainframe architecture
Server-based processing

18. Client/Server Architecture
Overview

19. Client/Server Architecture
Fat and Thin Clients

20. Client/Server Architecture
Client/Server Tiers
Two-tier design
Three-tier design
Middleware
Enables the tiers to communicate and pass data back and forth
Provides a transparent interface
Can integrate legacy systems and Web-based applications

21. Network Models The OSI Reference Model
The OSI model consists of seven layers
Each layer performs a specific function
Offers a set of design standards
Name 1 Network typology and describe it in your own words.

22. Chapter 11
Managing Systems Implementation

23. Next Steps
Now that you have developed your system, what are the steps involved in deploying and implementing your solution?

24. Application Development
System Development Tools
Entity-relationship diagrams
Flowcharts
Pseudocode
Decision tables and decision trees

25. Application Development
Project Management
Even a modest-sized project might have hundreds or even thousands of modules
Important to set realistic schedules, meet project deadlines, control costs, and maintain quality
Should use project management tools and techniques

26. Structured Application Development
Structure Charts
Control module
Subordinate modules
Module
Data Couple
Control Couple
Condition
Loop

27. Structured Application Development
Cohesion and Coupling
If you need to make a module more cohesive, you can split it into separate units, each with a single function
Loosely coupled
Tightly coupled

28. Structured Application Development
Drawing a Structure Chart
Step 1: Review the DFDs
Review all DFDs for accuracy and completeness
Step 2: Identify Modules and Relationships
Transform functional primitives or object methods into program modules
Three-level structure charts relate to the three DFD levels

29. Structured Application Development
Steps in Drawing a Structure Chart
Step 3: Add Couples, Loops, and Conditions
Identify the data elements that pass from one module to another
Step 4: Analyze the Structure Chart and the Data Dictionary
Ensure that the chart reflects all previous documentation and that the logic is correct

30. Agile Application Development
Is a distinctly different systems development method
Development team is in constant communication with the customer
Focuses on small teams, intense communication, and rapid development iterations
Extreme Programming (XP) is one of the newest agile methods

31. Agile Application Development
An extreme programming (XP) Example
User story
Release plan
Iteration cycle
Iteration planning meeting
Parallel programming
Test-driven design

32. Agile Application Development
The Future of Agile Development
Critics claim it lacks discipline and produces systems of questionable quality
Before implementing agile development, the proposed system and development methods should be examined carefully
A one-size-fits-all solution does not exist

33. Testing the System Unit Testing Integration Testing System Testing
You should regard thorough testing as a cost-effective means of providing a quality product

34. Documentation Program Documentation System Documentation
Operations Documentation
User Documentation
Systems analysts usually are responsible for preparing documentation to help users learn the system

35. Documentation User Documentation
Effective online documentation is an important productivity tool
Written documentation material also is valuable

36. Management Approval
After system testing is complete, you present the results to management
If system testing produced no technical, economical, or operational problems, management determines a schedule for system installation and evaluation

37. System Installation and Evaluation
Remaining steps in systems implementation:
Prepare a separate operational and test environment
Provide training for users, managers, and IT staff
Perform data conversion and system changeover
Carry out post-implementation evaluation of the system
Present a final report to management

38. Training Training Plan
The three main groups for training are users, managers, and IT staff
You must determine how the company will provide training
Vendor Training
Often gives the best return on your training dollars

39. Training
What types of training might be involved with TIMS system?

40. Data Conversion Data Conversion Strategies
The old system might be capable of exporting data in an acceptable format for the new system or in a standard format such as ASCII or ODBC
If a standard format is not available, you must develop a program to extract the data and convert it
Often requires additional data items, which might require manual entry

41. Data Conversion Data Conversion Security and Controls
You must ensure that all system control measures are in place and operational to protect data from unauthorized access and to help prevent erroneous input
Some errors will occur
It is essential that the new system be loaded with accurate, error-free data

42. System Changeover

43. System Changeover Direct Cutover
Involves more risk than other changeover methods
Companies often choose the direct cutover method for implementing commercial software packages
Cyclical information systems usually are converted using the direct cutover method at the beginning of a quarter, calendar year, or fiscal year

44. System Changeover Parallel Operation
Easier to verify that the new system is working properly under parallel operation than under direct cutover
Running both systems might place a burden on the operating environment and cause processing delay
Is not practical if the old and new systems are incompatible technically
Also is inappropriate when the two systems perform different functions

45. System Changeover Pilot Operation
The group that uses the new system first is called the pilot site
The old system continues to operate for the entire organization
After the system proves successful at the pilot site, it is implemented in the rest of the organization, usually using the direct cutover method
Is a combination of parallel operation and direct cutover methods

46. System Changeover Phased Operation
You give a part of the system to all users
The risk of errors or failures is limited to the implemented module only
Is less expensive than full parallel operation
Is not possible, however, if the system cannot be separated easily into logical modules or segments

47. System Changeover

48. Post-Implementation Tasks
Post-Implementation Evaluation
A post-implementation evaluation should examine all aspects of the development effort and the end product — the developed information system
You can apply the same fact-finding techniques in a post- implementation evaluation that you used to determine the system requirements during the systems analysis phase

49. Post-Implementation Tasks
Final Report to Management
Your report should include the following:
Final versions of all system documentation
Planned modifications and enhancements to the system that have been identified
Recap of all systems development costs and schedules

50. Post-Implementation Tasks
Final Report to Management
Your report should include the following:
Comparison of actual costs and schedules to the original estimates
Post-implementation evaluation, if it has been performed
Marks the end of systems development work

51. Final Project

52. Due Tuesday, March 13 Use the same groups as Midterm Project….
….unless I ask you to add a group member…
Same Procedures as before:
Plan your work NOW!
1 project submitted per group
Each person submits peer review
I will have project reviews from March 3 to March 8.
Final Project is worth 140 points

53. Final Project Requirements
System Architecture Tasks
Recommend TIMS system architecture with an overall network typology (10 pts)
Discuss how to handle
Legacy data (10 pts)
Web-centricity (10 pts)
Scalability (10 pts)
Security (10 pts)
Batch processing (10 pts)

54. Final Project Requirements
System Architecture Tasks
Prepare a design specification document (30 pts)
See “System Design Specification” under Forms Library
Systems Implementation
Develop a testing plan that includes unit testing, integration testing, and system testing. (10 pts)
Draft a reminder to staff on the importance of documentation. (10 pts)

55. Final Project Requirements
Systems, Operation, Support & Security
Draft a message to Jesse discussing the importance of capacity planning for TIMS
Be sure to describe capacity planning and make your recommendation on whether to include it in the project.

56. System Design Specification
Management Summary
System Component Details
Program Design
Output Design
Input Design
File & Database Design
Support Processing Design
Environmental IT Requirements
Implementation Requirements
Time & Cost Estimates
Each section should be at least ½ page. System Component section will be several pages.

57. Final Project Requirements
For each of the required elements:
Explain the topic in detail using terms that demonstrate you thoroughly understand the topic
Present your proposed solution for TIMS
Defend your solution with actual data and information from the SCR site.

58. Any Questions? Final Project Reviews
Office Hours via AIM
Thursday pm
Sunday pm
me 2 times for final project reviews.
Final Project Reviews
Saturday, March 3 7:00 pm to 9:00 pm
Sunday, March 4 morning or afternoon
Thursday, March 8 6:00 – 7:00 pm 7:00 – 8:00 pm 9:00 – 10:00 pm