1. 10 SYSTEMS DESIGN C H A P T E R Chapter 10 - Systems Design
This repository of slides is intended to support the named chapter. The slide repository should be used as follows:
Copy the file to a unique name for your course and unit.
Edit the file by deleting those slides you don’t want to cover, editing other slides as appropriate to your course, and adding slides as desired.
Print the slides to produce transparency masters or print directly to film or present the slides using a computer image projector.
Each slide includes instructor notes. To view those notes in PowerPoint, click-left on the View Menu; then click left on Notes View sub-menu. You may need to scroll down to see the instructor notes.
The instructor notes are also available in hardcopy as the Instructor Guide to Accompany Systems Analysis and Design Methods, 5/ed.
Chapter 10 - Systems Design

2. Chapter Ten Systems Design
Describe the design phase in terms of your information building blocks.
Identify and differentiate between several systems design strategies.
Describe the design phase tasks in terms of a computer-based solution for an in-house development project.
Describe the design phase in terms of a computer-based solution involving procurement of a commercial systems software solution.
No additional notes
Chapter 10 - Systems Design

3. Chapter Map
No additional notes
Chapter 10 - Systems Design

4. System Design
Information systems design is defined as those tasks that focus on the specification of a detailed computer-based solution. It is also called physical design.
Thus, whereas systems analysis placed emphasis on the business problem, systems design places emphasis on the technical or implementation concerns of the system.
No additional notes
Chapter 10 - Systems Design

5. System Design Approaches
Model-Driven
Modern structured design
Information engineering
Prototyping
Object-oriented
JAD
RAD
No additional notes
Chapter 10 - Systems Design

6. Modern Structured Design
Modern Structured Design is a process-oriented technique for breaking up a large program into a hierarchy of modules that result in a computer program that is easier to implement and maintain (change). Synonyms (although technically inaccurate) are top-down program design and structured programming.
The software model derived from structured design is called a structure chart.
Teaching Tips
You may query the students to see if they either developed or were provided with a structure chart in one of their programming courses.
Chapter 10 - Systems Design

7. Information Engineering
Information Engineering is a model-driven and data-centered, but process-sensitive technique to plan, analyze, and design information systems.
The primary tool of IE is a data model diagram.
Teaching Tips
You may refer the students to Chapter 7 for examples of a data model diagram.
Chapter 10 - Systems Design

8. Prototyping
The prototyping approach is an iterative process involving a close working relationship between the designer and the users.
Key Benefits:
Prototyping encourages and requires active end-user participation.
Iteration and change are a natural consequence of systems development – thus, it accommodates end-users whom tend to change their minds.
Prototyping endorses the philosophy that end-users wont know what they want until they see it.
Prototypes are an active, not passive, model that end-users can see, touch, feel, and experience.
An approved prototype is a working equivalent to a paper design specification, with one exception -- errors can be detected much earlier.
Prototyping can increase creativity because it allows for quicker user feedback, which can lead to better solutions.
Prototyping accelerates several phases of the life cycle, possibly bypassing the programmer.
Teaching Tips
Looking ahead, you might mention that the students will learn more about prototyping and perhaps do problems, exercises, and case study milestones that will require them to develop prototypes.
There are numerous PowerPoint slides of input, output, and dialogue screens provided with Chapters 13, 14, 15 respectively.
Chapter 10 - Systems Design

9. Object-Oriented Design (OOD)
Object-oriented design is the newest design strategy and is an extension of object-oriented analysis.
Object-oriented design (OOD) techniques are used to refine the object requirements definitions identified earlier during analysis, and to define design specific objects.
Teaching Tips
Refer the students to Modules A and B for more on the subject of object-oriented analysis and design.
Chapter 10 - Systems Design

10. Rapid Application Development (RAD)
Rapid application development (RAD) is the merger of various structured techniques (especially the data-driven information engineering) with prototyping techniques and joint application development techniques to accelerate systems development.
RAD calls for the interactive use of structured techniques and prototyping to define the users’ requirements and design the final system.
The expedition of the design effort is enhanced through the emphasis on user participation in Joint application development (JAD) sessions.
No additional notes
Chapter 10 - Systems Design

11. Joint Application Development (JAD)
Joint Application Development (JAD) is a technique that complements other systems analysis and design techniques by emphasizing participative development among system owners, users, designers, and builders.
During the JAD sessions for systems design, the systems designer will take on the role of facilitator for possibly several full-day workshops intended to address different design issues and deliverables.
No additional notes
Chapter 10 - Systems Design

12. Context Of In-House Development Projects
No additional notes
Chapter 10 - Systems Design

13. Design Phase Tasks For In-House Development
No additional notes
Chapter 10 - Systems Design

14. Sample Physical Data Flow Diagram
No additional notes
Chapter 10 - Systems Design

15. Sample Data Base Schema
No additional notes
Chapter 10 - Systems Design

16. Sample Output Design
No additional notes
Chapter 10 - Systems Design

17. Sample Interface Design
No additional notes
Chapter 10 - Systems Design

18. Context Of System Design For “Buy” Solutions To Projects
No additional notes
Chapter 10 - Systems Design

19. Design Phase Tasks For Commercial Software Solutions
No additional notes
Chapter 10 - Systems Design

20. Technical and Business Research Sources
Magazines and journals
Internal standards may exist for hardware and software selection.
Information services are primarily intended to constantly survey the marketplace for new products and advise prospective buyers on what specifications to consider.
Trade newspapers and periodicals offer articles and experiences on various types of hardware and software that you may be considering.
No additional notes
Chapter 10 - Systems Design

21. Typical Outline for Request For Proposal (RFP)
Request for Proposals (RFP) I.
Introduction A.
Background B.
Brief summary of needs C.
Explanation of RFP document D.
Call for action on part of vendor
II.
Standards and instructions
Schedule of events leading to contract
Ground rules that will govern selection decision 1.
Who may talk with whom and when 2.
Who pays for what 3.
Required format for a proposal 4.
Demonstration expectations 5.
Contractual expectations 6.
References expected 7.
Documentation expectations
III.
Requirements and features
Hardware
Mandatory requirements, features, and criteria
Essential requirements, features, and criteria
Desirable requirements, features, and criteria
Software
Service
Mandatory requirements
Essential requirements
Desirable requirements
IV.
Technical questionnaires V.
Conclusion
No additional notes
Chapter 10 - Systems Design