These notes cover the entire course relating to theory and enabled me to achieve 79% for the course. It is a Word document so that you can add and edit the notes to your liking.
1.6 (A) TESTING AND TEST CASES.............................................52
1.6 (B) SECURITY AND CONTROL...............................................66
,1.1. Moving to Design
Systems Design
The objective is to define, organize, and structure the components of the final
solution to serve as a blueprint for development.
Provides the starting point for systems development.
Provides the starting point for systems design.
Systems Development
Build, test and integrate system components (programming and component
integration) in accordance with chosen computer architecture and methodology.
Systems Implementation
Installing, testing and securing, and backing-up the system.
Process:
Analysis Design Implementation
Waterfall vs agile approach
, 1. Waterfall life cycle: clear transition between two activities (analysis and
design).
2. Agile/iterative approach: analysis of a specific part of the system will come
before its design, but analysis and design may be occurring in parallel.
NOTE: Best approach to use would be the Agile approach.
, Design VS Analysis
Throughout design, team considers new system in respect to
current environment and systems that exists with the organisation as a whole:
Environmental factors (e.g. integrating with an existing system).
Convert data from legacy systems.
Leveraging skills that exist in-house.
Getting UX (user experience) and UI (user interfaces) correct.
Key activities undertaken during design stage:
Examine several design strategies and decide which will be used to build
system.
Detailed design of individual classes and methods.
Designing UI, system inputs and outputs.
Making physical arch decisions regarding hard and software that will be
purchased to support new system.
Levels of Design
1. System Design: deals with the high-level architecture of the system -
structural aspects and standards that affect the overall system.
Hardware, network, and system software infrastructure.
Communication between sub-systems.
Standards for screens, reports, help etc.
2. Detailed design: adds detail to the analysis to provide a detailed system
specification.
Adds detail to analysis to provide detailed system specification.
Class design
Sequence design
UI and report design
Database design
Security and controls design
Design Activities
Describe the environment.
Design the application components.
Design the user interface.
Design the database.
Design the software classes and methods.
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 EFT, 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 this summary from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller joshbirkholtz. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy this summary for R50,00. You're not tied to anything after your purchase.
