Resume
Summary ICT2622 - Object Oriented Analysis Chapter 1
- Cours
- Établissement
- Book
ICT2622 - Object Oriented Analysis
[Montrer plus]
Livre connecté
Titre de l’ouvrage:
Auteur(s):
- Édition:
- ISBN:
- Édition:
Plus de résumés pour
-
ICT2622 Assignment 2 (COMPLETE ANSWERS) 2024 (390468)- DUE 7 August 2024 ; 100% TRUSTED Complete, trusted solutions and explanations. Ensure your success with us..
-
ICT2622 Assignment 2 (COMPLETE ANSWERS) 2024 (390468)- DUE 7 August 2024 ; 100% TRUSTED Complete, trusted solutions and explanations. Ensure your success with us..
-
ICT2622 Assignment 2 (DETAILED ANSWERS) 2024 - DISTINCTION GUARANTEED
Vendeur
S'abonner
Gideon007
Avis reçus
Aperçu du contenu
Information system a set of interrelated components that collect, process, store, and provide as output theinformation needed to complete ousiness tasks
Computer application or app a computer softare program that
executes on a computing device to carry out a specifc function or set
of related functions
Systems analysis those system development activities that enaole a
person to understand and specify what the net system should
accomplish
Systems design those system development activities that enaole a
person to descrioe in detail how the resulting information system till actually oe implemented
In a nutshell, systems analysis and design provides the tools and techniques you need as an
information system developer to complete the development process:
1. Understand the need (business need).
2. Capture the vision.
3. Defne a solution.
4. Communicate the vision and the solution.
5. Build the solution or direct others in building the solution.
6. Confrm that the solution meets the need.
7. Launch the solution application.
1. The System Development Life Cycle (SDLC)
System development life cycle (SDLC) a frametork that identifes all the activities required to research, ouild,
deploy, and ofen maintain an information system.
The six core processes required in the development of any information system:
■ Identify the problem or need and obtain approval to proceed with the
project.
■ 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—what is
required?
■ Design the system components that solve the problem or satisfy the need
— how will it actually work?
■ Build, test, and integrate system components—lots of programming and
component integration.
■ Complete system tests and then deploy the solution—the need now is
satisfed.
System development process or methodology a set of comprehensive
guidelines for carrying out all of the activities of each core process of the
SDLC
Agile development an information system development process that emphasizes feeibility and rapid
response to anticipate new and changing requirements during development
Iterative development is an approach to system development in which the system is “grown” piece
by piece through multiple mini projects called iterations.
There are several benefts to iterative development.
For one, portions of the system can sometimes be deployed sooner.
Second, by taking a small portion and developing it frst, the most difcult problems can be
identifed and addressed early in the project
Finally, developing a system in iterations makes the entire development process more feeible
and able to address new requirements and issues that come up throughout the project
Identify and document the specifc business need and to defne the project objectives. They might be
called pre-project activities of Core Process 1:
■ Identify the problem and document the objective of the solution system.
■ Obtain approval to commence the project.
, Day 1:
The project actually begins with Day 1, which is essentially a planning day. The second SDLC core
process—Plan and monitor the project—includes business analysis and project management activities.
These Core Process 2 activities are completed on Day 1:
■ Determine the major components (functional areas) that are needed.
■ Defne the iterations and assign each functional area to an iteration.
■ Determine team members and responsibilities.
Planning the Overall Project and the Project Iterations
As is often the case, the list of system capabilities provides the foundation information for determining
the overall project plan. The frst step is to divide the system into several subsystems or components.
Subsystem is an identifable and fully functional part of a complete system
Planning the Rest of the First Iteration: The Supplier Subsystem
The planning process for an iteration consists of these three steps:
■ Identify the tasks required for the iteration.
As these tasks are identifed, they are compiled and organized. Sometimes, this organized list of
tasks is called a work breakdown structure (WBS)
Part of this efort is trying to estimate how long each task will take. (in hours)
■ Organize and sequence these tasks into a schedule.
We can be very formal and use a sophisticated project scheduling tool, or we can just list the
tasks in the order we think they need to be done.
The beneft of an iteration schedule is threefold. First, it helps the team organize its work so
developers have enough time to think through the critical design issues before programming
begins. Second, it provides a measuring rod to see if the iteration is on schedule.
■ Identify required resources (especially people), and assign people to tasks.
Day 2:
Day 2 involves discovering and understanding details, which is a key part of systems analysis.
These Core Process 3 activities include:
■ Do fact-fnding tasks to understand the requirements.
Before the project commenced, a broad defnition of requirements was developed.
There are various techniques to ensure that the fact fnding is complete and thorough. These
include interviewing the key users, observing eeisting work processes, reviewing eeisting
documentation and eeisting systems, and even researching other companies and other systems.
The frst step is to identify the key users who will defne these details.
■ Develop a list of use cases and a use case diagram.
Identifying and describing use cases is the way to document what the users need to do with the
system
“The purchasing agent ‘uses’ the system to ‘Look up a supplier.’”
■ Develop a list of classes and a class diagram
Domain classes identify those things in the real world that the system needs to know about and
keep track of.
We look for all objects, or things, that the system uses or captures. Objects come in all types
and variations, from tangible items (such as merchandise products that you can see and touch)
to more abstract concepts that you cannot touch (such as a promotion).
Domain classes are the categories of objects identifed, much like a table in a database
represents the category of the records it contains.
Les avantages d'acheter des résumés chez Stuvia:
Qualité garantie par les avis des clients
Les clients de Stuvia ont évalués plus de 700 000 résumés. C'est comme ça que vous savez que vous achetez les meilleurs documents.
L’achat facile et rapide
Vous pouvez payer rapidement avec iDeal, carte de crédit ou Stuvia-crédit pour les résumés. Il n'y a pas d'adhésion nécessaire.
Focus sur l’essentiel
Vos camarades écrivent eux-mêmes les notes d’étude, c’est pourquoi les documents sont toujours fiables et à jour. Cela garantit que vous arrivez rapidement au coeur du matériel.
Foire aux questions
Qu'est-ce que j'obtiens en achetant ce document ?
Vous obtenez un PDF, disponible immédiatement après votre achat. Le document acheté est accessible à tout moment, n'importe où et indéfiniment via votre profil.
Garantie de remboursement : comment ça marche ?
Notre garantie de satisfaction garantit que vous trouverez toujours un document d'étude qui vous convient. Vous remplissez un formulaire et notre équipe du service client s'occupe du reste.
Auprès de qui est-ce que j'achète ce résumé ?
Stuvia est une place de marché. Alors, vous n'achetez donc pas ce document chez nous, mais auprès du vendeur Gideon007. Stuvia facilite les paiements au vendeur.
Est-ce que j'aurai un abonnement?
Non, vous n'achetez ce résumé que pour €0,00. Vous n'êtes lié à rien après votre achat.
Peut-on faire confiance à Stuvia ?
4.6 étoiles sur Google & Trustpilot (+1000 avis)
79373 résumés ont été vendus ces 30 derniers jours
Fondée en 2010, la référence pour acheter des résumés depuis déjà 14 ans