Summary
Summary ICT2622 Summarised Study Notes
- Institution
- University Of South Africa (Unisa)
Latest exam pack questions and answers and summarized notes for exam preparation. for assistance. All the best on your exams!!
[Show more]
Connected book
Book Title:
Author(s):
- Edition:
- ISBN:
- Edition:
Content preview
ICT2622NOTES
,Systems Analysis and Design in a Changing World, sixth edition 1-1
Chapter 1 - From Beginning to End: An Overview of Systems
Analysis and Design Lecture Notes
Table of Contents
Chapter Overview
Learning Objectives
Chapter Overview
The sixth edition of Systems Analysis and Design in a Changing World is a completely new and
innovative approach to teaching systems analysis and design. The intent of this new approach is to
provide a much more example based learning opportunity. As such the entire first chapter is an
example of a complete development project from beginning to end. Obviously, in a single chapter
example, not every step is elaborated. However, by going through the entire process, you will be able to
obtain a broad overview and a clear perspective of the entire development process.
The chapter first introduces several basic concepts that are needed to understand systems development.
The first few sections define Systems Analysis, Systems Design, the Systems Development Life Cycle
(SDLC), iterative development, Agile development and the six core processes of systems development.
The remainder of the chapter illustrates the first iteration of a typical development project for the
Ridgeline Mountain Outfitters (RMO) Tradeshow system. It divides the project into seven steps,
including pre-project activities and then six other development steps. For simplicity purposes, each step
is assigned a day, so the project has Day 1 activities, Day 2 activities, etc. Throughout this set of daily
activities, all six core processes are explained and illustrated. Sample models and diagrams are
presented to give you an introduction to some of the major techniques and models that will be taught
later in the text. Please be aware that most projects especially large complex projects take weeks
sometimes months even years. The book is just making it simpler by presenting it by days.
Your assignments will be to work on a running case similar to the RMO Tradeshow system case. I
assume that the students in this class have various levels of systems development background. So you
may not have all of the skills necessary to do an error-free complete development assignment. The
objective of the case and its assignments is simply to allow you to practice going through the entire
development process so that you obtain a solid overview of systems development. My philosophy on
grading is that you must give it your best effort. I am not looking for perfect submissions. I am
looking for whether you read the book, understood the concepts, tools, techniques enough to apply
them to the case assignment. I will know if you did not give it your best effort. Meaning you
submitted it last minute, did the minimum just to submit something by the deadline, and/or you did a
sloppy job. Trust me I can tell. I suggest that you submit the assignment early with your best effort. If
there’s time and I think you can improve on your work, then I will allow for resubmission for more
points. It is completely at my discretion whether I will allow you to resubmit the assignment or not. If
it is on the due date then most likely I will NOT allow for resubmission. I want to mentor you through
the case study. Don’t be shy about sending me questions if you are confused. This is NOT a license
for me to review your work before you submit and do pre-grading. Be specific about your question(s)
and attach your file(s). I will help you out.
,Systems Analysis and Design in a Changing World, sixth edition 1-2
Learning Objectives
After reading this chapter, you should be able to:
Describe the purpose of systems analysis and design in the development of information system
Describe the characteristics of iterative systems development
Explain the six core processes of the Systems Development Life Cycle
Identify key documents that are used in planning a project
Identify key diagrams used in systems analysis and systems design
Explain the utility of identifying use cases in systems development
Explain the utility of identifying object classes in systems development
Software Development and Systems Analysis and Design
Key Terms
computer application (app)—a computer software program that executes on a computing
device to carry out a specific function or set of related functions
information system—a set of interrelated computer components that collects, processes, stores,
and provides as output the information needed to complete business tasks
systems analysis—those activities that enable a person to understand and specify what the new
system should accomplish
systems design—those activities that enable a person to define and describe in detail the system
that solves the need
The objective of this section is to introduce you to the basic concepts of a computer application and
an information system. The section includes an introduction to and definition of systems analysis and
design and explains how it fits into the process of developing a new information system, i.e. systems
development. Systems analysis means to understand what the system must do. Systems design means
to specify how the components are configured to provide the solution.
Systems Development Life Cycle
Key Terms
project—a planned undertaking that has a beginning and an end, and that produces some
definite result
Systems Development Life Cycle (SDLC)—the entire process consisting of all the activities
required to build, launch, and maintain an information system
information systems development process—the actual approach used to develop a particular
information system
Agile Development—an information systems development process that emphasizes flexibility
, Systems Analysis and Design in a Changing World, sixth edition 1-3
to anticipate new requirements during development
The second section in this chapter is an explanation of the Systems Development Life Cycle (SDLC).
The SDLC defines all the activities required to develop a new system. There are many different
versions of the SDLC. This section presents the six core processes required for the development of any
new system. In other words, these six core processes are common to all types of SDLCs. By
understanding these six core processes, you will not only be able to develop new systems effectively,
but you will be able to adapt to any other SDLC that you may encounter in industry. The six core
processes are: [Note: These six core processes are used throughout the textbook.]
1. Identify the problem or need and obtain approval to proceed.
2. Plan and monitor the project—what to do, how to do it, and who does it.
3. Discover and understand the details of the problem or the need.
4. Design the system components that solve the problem or satisfy the need.
5. Build, test, and integrate system components.
6. Complete system tests and then deploy the solution.
This section also introduces Agile Development as an iterative approach to systems development.
Agile development will be covered in more detail in Chapter 8, but an introduction is appropriate and
required in the context of the example in the chapter.
Agile projects must be agile and flexible. They must have procedures in place to allow for, anticipate,
and even embrace changes and new requirements during the development process.
It is important to understand that all projects are not linear, point A to point B. There are always things
that change throughout the systems development life cycle (SDLC). So information technology (IT)
professionals, users and management have to be flexible and receptive to changes. That does NOT
mean that every project will be chaotic. The project manager must be very skilled in managing the
changes and the project team and management must understand the changes. So a good change control
process should be implemented.
Please note that the following case (RMO) is an example of software development. The many other
types of systems development projects such as upgrading a new network. The majority of projects are
software projects or have software components.
Introduction to Ridgeline Mountain Outfitters
The next section introduces Ridgeline Mountain Outfitters (RMO). RMO is a sportswear company that
sells both its own branded products as well as well as other national brands. There are two systems for
RMO that are discussed in the textbook. The Tradeshow system is a small system that serves as the
example development project in Chapter 1. The Consolidated Sales and Marketing System (CSMS) is
a major system that serves as the running example throughout the rest of the textbook. This chapter
only introduces RMO and the Tradeshow system.
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through EFT, credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying this summary from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller iStudy. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy this summary for R50,00. You're not tied to anything after your purchase.
Can Stuvia be trusted?
4.6 stars on Google & Trustpilot (+1000 reviews)
66579 documents were sold in the last 30 days
Founded in 2010, the go-to place to buy summaries for 14 years now