Other
Unit 22 - Systems Analysis and Design Assignment 2
- Institution
- PEARSON (PEARSON)
Unit 22 - Systems Analysis and Design Assignment 2
[Show more]
Content preview
UNIT 22: SYSTEMS ANALYSISAND DESIGN
Examine the principles of systems analysis and design
,Contents
A1: Development Models............................................................................................................................2
Information System.................................................................................................................................2
Software Development life cycle (SDLC)..................................................................................................2
Waterfall model...................................................................................................................................3
Agile model..........................................................................................................................................4
Iteration model....................................................................................................................................5
RAD(Rapid Application Development) Model......................................................................................6
SCRUM Agile Methodologies...............................................................................................................7
A2: Systems analysis tools and techniques..................................................................................................9
Data Flow Diagrams (DFD).......................................................................................................................9
Context Diagram (Level 0)....................................................................................................................9
DFD Level 1..........................................................................................................................................9
DFD Level 2 or higher.........................................................................................................................10
Computer-aided Software Engineering (CASE)......................................................................................11
Structured Systems Analysis and Design Method (SSADM)...................................................................13
Feasibility Study.................................................................................................................................13
Requirements Analysis Stage.............................................................................................................13
Requirements Specifications Stage....................................................................................................14
Technical System Specification Stage................................................................................................14
Logical System Specification Stage........................................................................................................14
Physical Design Stage.............................................................................................................................14
Unified Model Language (UML).............................................................................................................14
Structured Diagrams..........................................................................................................................14
Behavioural Diagrams........................................................................................................................15
Suitability of methods for different programming paradigms...............................................................17
Busines Process Reengineering..................................................................................................................17
Map the current state of your business processes............................................................................17
Analyse them and find any process gaps or disconnects...................................................................17
Look for improvement opportunities and validate them...................................................................17
Design a cutting-edge future-state process map...............................................................................17
Implement future state changes and be mindful of dependencies...................................................18
, Evaluation..................................................................................................................................................18
References.................................................................................................................................................19
A1: Development Models
Information System
An information system is made of components/tool where its purpose is to assist in the collection of
data, storing data, manipulation of data to our needs. Many Businesses and organisations rely on in
Information Systems for their operations to function as it allows organisations to more effectively
process and store information. For example, in retail, eBay or Amazon will use information systems to
automate their business processes like orders. User recommendation based on what they viewed etc.
Software Development life cycle (SDLC)
A Lifecyle methodology in developing and maintaining software which is composed of multiple phases to
assist an organization in the creation of a software. Common SDLC models are waterfall, spiral and agile.
- Requirement Gathering And analysis
o The most crucial part of any software development project. Its purpose is to gather
information and analyse what is needed of the system to do when it deployed. This
phase gathers requirements from stakeholders in the project, end users and any related
teams to gather information develop and propose potential plans for the next step for
deeper analysis.
- System Analysis
o This phase analyses the project is feasible for business and would provide some form for
benefit in creating the system. This phase will break the system plan it detail and into
individual parts making it more significantly to work as they are more manageable for
the organisation to develop and create. This allows parts to be properly prioritised to
ensure components of system can be properly planned which reduces the dangers of
potential risks in the future.
- System design
o This stage leads on from system analysis where the system is completely designed and
planned before development begins. The purpose to understand how the system will
perform functions, looks and how it is built. This helps to ensure their proper
functionality to users when its deployed as well act as guide for development team
when creating the system
- Software development
o The creation of the system. This phase has multiple processes from developing the
software code, infrastructure the system may need like back-end server or database and
documentation on how to operate and use the system. Software development allocates
tasks for developers, so developers are aware they are required to work optimising
efficiency.
- Testing
o When the first version of a system is developed before it is released it goes through
phase called testing to ensure it works as it was intended for. This is done by QA(Quality
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 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 yetech. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for £7.99. You're not tied to anything after your purchase.
Can Stuvia be trusted?
4.6 stars on Google & Trustpilot (+1000 reviews)
64438 documents were sold in the last 30 days
Founded in 2010, the go-to place to buy revision notes and other study material for 14 years now