Lee, Aaron Joshua I.
10756817
BS-Im
Sysanal
Title: System Analysis and Design
Second Edition
Author: Alan Dennis and Barbara Haley Wixom
Reference Number: QA 76.9 S88 D45 2003
Book Review:
Chapter 1: The System Development Life Cycle
“All system development projects follow essentially the same fundamental
process called the system development life cycle (SDLC). SDLC starts with a
planning phase in which the project team identifies the business value of the
system, conducts a feasibility analysis, and plans the project. The second phase is
the analysis phase, in which the team develops an analysis strategy, gathers
information, writes use cases, builds a process model, and builds a data model. In
the next phase, the design phase, the team develops the physical design,
architecture design, interface design, data storage design, and program design. In
the final phase, implementation, the system is built installed, and maintained.”
The SDLC is a well-rounded system that both analysis and creator use.
System analysts before analyzing something they need something like the SDLC
to produce an effective analysis. Same thing as for the creators in creating a new
system or a startup the creator needs the SDLC to develop their product into
something that is efficient as well effective to its end-users. The phases that the
SDLC goes through are what make an analysis; startups and systems top its
market.
Lee, Aaron Joshua I.
10756817
BS-Im
Sysanal
Title: System Analysis and Design
Second Edition
Author: Alan Dennis and Barbara Haley Wixom
Reference Number: QA 76.9 S88 D45 2003
Book Review:
Chapter 1: System Development Methodologies
“Structured design methodologies, such as waterfall and parallel
development, use a formal step-by-step approach to the SDLC that moves
logically from one phase to the next (and makes it hard to reverse direction). They
produce a solid, well-through-out system but can overlook requirements because
users must specify them early in the design process before seeing the actual
system. Rapid application development (RAD) methodologies attempt to speed up
development and make it easier for users to specify requirements by having parts
of the system developed sooner and either by producing different versions
(phased development) or by using prototypes (prototyping, throwaway
prototyping). Agile development methodologies focus on streamlining the DSLC
by eliminating many of the tasks and the time associated with requirements
definition and documentation. The choice of a methodology is influenced by the
clarity of the user requirement, familiarity with the base technology, system
complexity, and the need for system reliability, time pressures, and the need to see
progress on the tie schedule.”
Not only by SDLC is the way in producing effective outputs. But,
Different Methodologies are used to develop an efficient technology for further
innovation. These help developers and analysts to manipulate different methods
to complement the project’s needs.
Lee, Aaron Joshua I.
10756817
BS-Im
Sysanal
Title: System Analysis and Design
Second Edition
Author: Alan Dennis and Barbara Haley Wixom
Reference Number: QA 76.9 S88 D45 2003
Book Review:
Chapter 1: Project Team Roles and Skills
“The project team needs a variety of skill. All analysts need to have
general skills, such as technical, business, analytical, interpersonal, management,
and ethical. However, different kinds of analysts require specific skills in addition
to these. Business analysts usually have business skills that help them to
understand the business issues surrounding the system, whereas systems analysts
also have significant experience in analysis and design and programming. The
infrastructure analyst focuses on the technical issues surrounding how the system
will interact with the organization’s technical infrastructure, and the change
management issues surrounding the system installation. In addition to analyst,
project teams will include a project manager, programmers, technical writers, and
other specialists.”
This is best way to define as instruction relating questions and technology
relative to the user’s everyday lives to their environment. Some organizations and
technology requires one person to be able to do many roles. This is where the
interpersonal abilities of a person come in, wherein here a person shows his
purpose and roll for the project’s development.
Lee, Aaron Joshua I.
10756817
BS-Im
Sysanal
Title: System Analysis and Design
Second Edition
Author: Alan Dennis and Barbara Haley Wixom
Reference Number: QA 76.9 S88 D45 2003
Book Review:
Chapter 2: Project Initiation
“Project initiation is the point a t which an organization creates and
assesses the original goals and expectations for a new system. The first step in the
process is to identify the business value for the system by developing a system
request that provides basic information about the proposed system. Next the
analysts perform a feasibility analysis to determine the technical, economic, and
organizational feasibility of the system, and if appropriate, the system is
approved, and the development project begins.”
A project initiation is the logical documentary whose purpose is to bring
together the significant details needed to establish the project on a converse basis;
and to put into words information to all concerned with the project. To be brief,
this is the, "who, why, what, when and how", part of the project. It defines all
major aspects of a project and forms the basis for its management and the
assessment of overall success.
Also, this is where members of the project are rate on whether they are
adequate to be part of the developing team.