Baylor Sullivan MIS 3320 Exam Review questions and answers 2024/2025
3 views 0 purchase
Course
MIS 3320 BAYLOR
Institution
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
Written for
MIS 3320 BAYLOR
All documents for this subject (17)
Seller
Follow
ACADEMICAIDSTORE
Reviews received
Content preview
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?
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 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 these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller ACADEMICAIDSTORE. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $10.89. You're not tied to anything after your purchase.
