Baylor Sullivan MIS 3320 Exam Review questions and answers 2024/2025
3 keer bekeken 0 keer verkocht
Vak
MIS 3320 BAYLOR
Instelling
MIS 3320 BAYLOR
Baylor Sullivan MIS 3320 Exam Review questions and answers 2024/2025
What is a system analyst? and what is the main role of a systems analyst?
System development activities that enable a person to understand and specify what the new system should accomplish. Main role - the analysis and design of...
baylor sullivan mis 3320 exam review questions and
Geschreven voor
MIS 3320 BAYLOR
Alle documenten voor dit vak (17)
Verkoper
Volgen
ACADEMICAIDSTORE
Ontvangen beoordelingen
Voorbeeld van de inhoud
Baylor Sullivan MIS 3320 Exam Review
questions and answers 2024/2025
What is a system analyst? and what is the main role of a systems analyst?
System development activities that enable a person to understand and specify what the new system
should accomplish. Main role - the analysis and design of information systems, most importantly
problem solving.
What skills are necessary to be a successful systems analyst?
Technical, business people
Technical
DB, programming, computer hardware, networking, operating systems, utilities, communication and
collaboration technology, SDLC Techniques
Business
Organizational knowledge, management techniques, functional work processes
People
Communication skills, interpersonal skills, roles - negotiator, teacher, mentor, collaborator, manager
What is the difference between a tool and a technique?
Tool: a software application that assists developers in creating models or other components required
for a project - usually use an SDLC to manage the project
Technique: guidelines to specify a method for how to carry out a development activity or task.
What is a systems development project?
A planned undertaking that produces a new information system.
What is an SDLC?
Framework that identifies all the activities required to research, build, deploy, and often maintain an
information system.
6 phases of an SDLC
Project initiation, Planning, Analysis, Design, Implementation, Deployment
SDLC core processes
1. Identify the problem or need and obtain approval to proceed with the project
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 - what is required
4. Design the system components that solve the problem or satisfy the need - how will it actually work
5. Build, test, and integrate system components - lots of programming and component integration
6. Complete system tests and the deploy the solution - the need now is satisfied
Approaches to the SDLC - SDLD
A fundamental concept in the success of information system development projects. Provides a way to
think about the development of a new system as a progressive process, much like a living entity.
, Approaches to the SDLC - Predictive
Requirements well understood and well defined (when the clients know exactly what they want). Low
technical risk
Approaches to the SDLC - Adaptive
Requirements and needs uncertain (the client doesn't know much of what they want). High technical
risk
Describe the Waterfall model?
An SDLC approach that assumes the phases can be completed sequentially with no overlap.
What are the problems with the Waterfall model?
System requirements "locked in", limited user involvement, too much focus on milestone deadlines
(have to do all of the analysis and then the design can be done)
Describe the modified Waterfall.
Overlapping phases, can go backwards, things can now be done faster
Describe the Spiral Model
An interactive approach, Spiral until project completion, then deployed to the user
project management: managed differently than a waterfall approach
advantage: client gets to see something sooner and much faster
Describe incremental development?
The system is built in small increments, it is "grown"
- as an iteration is completed it is integrated to the whole
- partially deployed in steps
- advantages: some functionality gets into the user's hands much earlier
What is a methodology?
Provides guidelines for every facet of the system development life cycle. "a comprehensive guideline
to follow for completing every SDLC activity"
Differences between Methodology and tools
software to create models or other project components (record info and write the code)
Differences between Methodology and techniques
guidelines or instructions (how the team will do the work) how to instruct an interview.
Differences between Methodology and models
abstraction used to separate out aspect (used to describe and specify the requirements) like
diagrams.
What is the difference between requirements and evolutionary prototyping?
Voordelen van het kopen van samenvattingen bij Stuvia op een rij:
Verzekerd van kwaliteit door reviews
Stuvia-klanten hebben meer dan 700.000 samenvattingen beoordeeld. Zo weet je zeker dat je de beste documenten koopt!
Snel en makkelijk kopen
Je betaalt supersnel en eenmalig met iDeal, creditcard of Stuvia-tegoed voor de samenvatting. Zonder lidmaatschap.
Focus op de essentie
Samenvattingen worden geschreven voor en door anderen. Daarom zijn de samenvattingen altijd betrouwbaar en actueel. Zo kom je snel tot de kern!
Veelgestelde vragen
Wat krijg ik als ik dit document koop?
Je krijgt een PDF, die direct beschikbaar is na je aankoop. Het gekochte document is altijd, overal en oneindig toegankelijk via je profiel.
Tevredenheidsgarantie: hoe werkt dat?
Onze tevredenheidsgarantie zorgt ervoor dat je altijd een studiedocument vindt dat goed bij je past. Je vult een formulier in en onze klantenservice regelt de rest.
Van wie koop ik deze samenvatting?
Stuvia is een marktplaats, je koop dit document dus niet van ons, maar van verkoper ACADEMICAIDSTORE. Stuvia faciliteert de betaling aan de verkoper.
Zit ik meteen vast aan een abonnement?
Nee, je koopt alleen deze samenvatting voor €10,30. Je zit daarna nergens aan vast.
