1 / 18

Structured Systems Analysis

Structured Systems Analysis. What we will cover. System modelling generally What is a model? Why model a system A summary of modelling approaches. The System. System modelling generally. O u t p u t s. Source 1. Recipient 1. I n p u t s. And lo …. Source 2. Recipient 2.

dylan-robertson
Download Presentation

Structured Systems Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Structured Systems Analysis

  2. What we will cover • System modelling generally • What is a model? • Why model a system • A summary of modelling approaches

  3. The System System modelling generally O u t p u t s Source 1 Recipient 1 I n p u t s And lo … Source 2 Recipient 2 a miracle happens! Source 3 Recipient 3

  4. What is a model? • That was a model! • An abstracted representation of something that enables the identification of relevant elements, components and their inter-relationships • For example: • An OS map of North Staffordshire • A YHA map of North Staffordshire • A cycling map of North Staffordshire • A road map of North Staffordshire • All show the same territory, but …

  5. Why model a system? • to find out what is and/or what should be going on • to allow system developers to understand and communicate with system users/sponsors • to provide a framework that handles complexity, allowing decomposition • it’s cheaper to model than to build • enables “look ahead”

  6. Why model a system? - summary • Enables you to “go there” in your head before you write any code • things can be identified and sorted into the important and the not-so-important • problems can be identified (and possibly even solved) early • clarifies woolly ideas • allows issues to be raised and discussed early • facilitates more sensible decisions • helps you to find out what you don’t know • saves embarrassment later

  7. Modelling/development approaches • Object oriented approaches • Structured approaches • Collaborative approaches • RAD, Prototyping, DSDM • ……. • Agile approaches • SCRUM, XP etc • Today’s challenge – what does SCRUM stand for? • prizes next time • Other approaches

  8. Structured modelling • Separates the consideration of: • what a system does (or is to do) from • the data and the (relational) data structures that are required to enable it to do it • Is all Edgar Codd’s fault (from 1970) • Process modelling - covers the what • Data modelling - covers the structure of the data needed to support what is happening • Time and Event modelling – cover things that Process Modelling doesn’t do very well • Structured modelling includes some useful techniques that are generically applicable

  9. Process Modelling • does what it says on the tin! • for any information system, models • processes (at various levels of detail) • participants • data required/processed/stored/transmitted • pictures give framework for detailed descriptions

  10. Data Modelling • Models the data required to enable a system to perform it’s defined functions (processes) • and how this data should be structured when persisting • Loads more of this later in the module • This is an area which improved greatly with practice and, at first, seems incomprehensible and impossible

  11. Useful structured modelling tools and techniques • Included here as they do not really fit neatly into the process and/or data categories • Aim of a system • Levelling • Problem/Requirements lists • Data dictionary • But, Process and Data modelling are implicitly included!

  12. Aim of a system • a (short) paragraph to define succinctly what a system does (and does not) do • For a company’s retail system • “To support the correct administration and accounting of ordering, packaging and sales of goods through its shop and mail order operations”

  13. Aim of a system - examples • A payroll system • “To enable the correct calculation of gross pay and deductions for all weekly paid employees. Funds will be transferred electronically.” • A lift system • “To transport a maximum of eight people between floors in a safe and timely manner”

  14. Levelling • Found in SAD structured process modelling but generically applied often • Handles complexity through grouping of low level functions and/or by decomposing high level functions • Each level lower has more detail than higher level(s) • Links high and low level functions allowing simultaneous consideration of all levels

  15. Something less complex Something less complex Something less complex Something less complex Something simpler Something simpler Something simpler Something simpler Something even simpler Something even simpler Something even simpler Something even simpler Levelling - graphically Something complex

  16. Problem/Requirements list • A numbered list of all the problems with the current system and (usually hence) requirements of a new system • Does not differentiate between whether issue is a problem or a requirement • Includes the sublime, the ridiculous and all points between • Serves as a check-list when conceiving and designing new system • Helps to prevent problems and requirements becoming lost in the maw (mire) of analysis and design methods

  17. What we have covered • System modelling generally • Consideration of a model and what it is • Why model a system • Identification of different modelling approaches. • Elements of structured approaches • Assignment guidance • What comes next

  18. References • Essentials of Systems Analysis and Design, Valachi, George and Hoffer, Pearson Prentice Hall • Software Engineering, Ian Sommerville, Addison Wesley, 2000 • Software System Development – A Gentle Introduction – Briton and Doake, McGraw Hill

More Related