Chapter 1 Review Questions

1. The difference between an information system and a computer application

is that an info system can include software, database, and manual related
processes. Whereas, a computer application includes only the computer
software.
2. The purpose of systems analysis is to describe in detail the what that a
system must do to satisfy the need or to solve the problem. The systems
analysis is important because it provides details on all the functions of a
system. Essentially, it allows the individual to understand and specify what a
system is doing or what it should do.
3. The difference between systems analysis and systems design is that
systems analysis deals with what a software system should accomplish and
systems design deals with how the system will accomplish the end result.
Said differently, the systems design deals with solving the systems problem
whereas the systems analysis deals with what the end goal of the new
system should be.
4. A project is a planned undertaking that has a beginning and an end, and
that produces some definite result.
5. The 6 processes for software systems development are:
- Identify the problem or need and obtain approval to proceed.
- Plan and monitor the project. (What to do, how to do it, and who does
it)
- Discover and understand the details of the problem or the need.
- Design the system components that solve the problem or satisfy the
need.
- Build, test, and integrate the systems components.
- Complete systems tests and deploy the solution.
6. Agile development refers to an information systems development process
that emphasizes flexibility to anticipate new requirements during
development. Agile development embraces the fact that no one knows all
the problems therefore the way you go about developing the product is
through agile development where changes are taken into account once they
are realized. Hence the flexibility aspect of agile development.
7. The purpose of a systems vision document is to identify the benefits and
capabilities included with in the systems. The specific document contains a
product description, a list of the systems capabilities, and a list of the
businesses benefits gained by the new system.

Chapter 1 Review Questions

8. By definition a subsystem is an identifiable and partitioned portion of an

overall system. The system is the entire software program (if you will). The
system is described in detail through the system capabilities in the systems
vision document. The subsystem(s) are derived from the systems capabilities
in the systems vision document. What the subsystems do is they categorize
the systems capabilities into chunks. Once the subsystem has been
identified it can then be handed out to project teams to develop.
9. Essentially, a work breakdown structure is an organized list of tasks that
need to be accomplished in order for the project to succeed. A work
breakdown structure is devised after all the tasks have been identified.
Identifying all the tasks is the first step in the planning of the first iteration.
The purpose of the work breakdown structure is to have the tasks listed
thataway the next steps can be carried out which are organizing and
sequencing the tasks into a schedule, and identifying the required resources
& assign the proper people to them.
10. The components of the work breakdown structure (WBS) are as follows:
- Discover and understand the details of the all aspects of the problem.
- Design the components of the solution to the problem.
- Build the components and integrate everything into the solution.
- Perform all systems level tests and deploy the solution.
11. By definition a use case is a methodology used in system analysis to
identify, clarify, and organize system requirements. The information that a
use case diagram provides is as follows:
- The boundary, which defines the system of interest in relation to the
world around it
- The employees, usually individuals involved with the system are
defined according to their roles
- The use cases, which are the specific roles played by the employees
within and around the system
- The relationships between and among the employees and the use
cases
12. A class diagram provides information about classes, their attributes and
their relationships. Essentially, a class diagram takes the object class which
is the things in the real world that the system needs to know and [the class
diagram] examines the relationship between each object class in a visual
manner.

Chapter 1 Review Questions

13. The use case diagram involves the business of the project and shows
who will utilize the system and the use case diagram also shows what
services the program provides. For example, the use case would in relation
to how the user will go about functioning the system. On the other hand, a
class diagram involves more of the architecture of the system. This is to say
the class diagram relates all the functions of the module in a way that allows
the developer to understand how the system will function. However there is
not usually code involved in the class diagram and instead just a quick
overview of the relationship between all the functions of the systems.
14. The activity diagram shows how the end user will manipulate the system.
It shows the sequential of the activity. It describes the person who will do
each activity. Lastly, it shows the activities that can be done by the user. In a
nutshell it presents to the viewer how the activities of the system are and
how they will go about being accomplished through the user and the users
responsibilities.
15. As it relates to user interface the activity diagram provides the ability to
accurately depict the dynamic aspect of virtually all current user interfaces.
Activity Diagrams give you the ability to construct a "roadmap" of user
functionality that accurately represents the paths a user can follow. Specific
types of user interface needs that the activity diagram can help to define are
the appearance of the systems, the controls of the systems (manage state),
and the navigation. These three aspects all relate to the user interface and
are developed and or thought of through the depiction in the activity
diagram.
16. The purpose of architectural design is to determine the overall structure
and form of the solution before trying to design the details.
17. What design class diagrams have that class diagrams do not is the object
oriented programming (OOP) classes. Said differently the class diagram does
not contain OOP.
18. Systems testing includes the following steps:
- start
- create test data
- conduct tests
- Document Errors and issues
- fix errors
- return back to the conduct tests step

Chapter 1 Review Questions

- From here you either find more errors and report them or you are
done given that you fixed all the errors.
19. The purpose of user acceptance testing is to have the user test the
system in order to determine the correctness of the system and to test its
fitness to accomplish the business requirements.
20. Dividing your project into separate iterations is a good idea because it
enables you to incrementally deliver capabilities (such as an executable,
usable subset of implemented and tested requirements) that can be
assessed by stakeholders at the end of each iteration. This provides rapid
and timely feedback loops, so that issues can be addressed and
improvements made at a lower cost. Also, this is accomplished while you still
have sufficient budget and time left to do so, and you have not gone so far
ahead that major rework is required.
21. The goal with iteration planning is to establish a few high-level objectives
for what to accomplish during the iteration, produce a sufficiently detailed
plan outlining who needs to do what to accomplish those objectives, and
define how to assess that you accomplished what you set out to accomplish.