1 / 14

Streamlining SSAD

This guide provides a comprehensive overview of streamlining the Systematic Software Application Development (SSAD) process, categorizing activities from perspectives of administration, design, programming, and operation. It discusses the conceptual, technical, and operational systems, along with methods to define, design, and develop them. Interactive approaches focus on key questions regarding documentation, request handling, and development strategies. With insights on using CASE tools and various documentations (PRD, PSD, SDD, SOM, WDSC), this resource aims to enhance communication and efficiency in system development.

xena
Télécharger la présentation

Streamlining SSAD

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. Streamlining SSAD PADT: Perspectives, Activities, Documents, and Tools

  2. Administrator Maintainer Designer Programmer Operator Three System Perspectives SSAD Define Request Conceptual System Technical System Design Revise Operational System Develop Run

  3. Three System Perspectives • Questions (focus-shifting activities): • How to define a system (conceptually)? • How to design a system (technically)? • How to develop a system (operationally)?

  4. R- and D-type Activities • R- / D Interactive Activities • Request vs Definition (Conceptual) • Reviewing vs Design (Technical) • Running vs Development (Operational)

  5. R- and D-type Activities • R- / D Interactive Activities • Request vs Definition (Conceptual: What-to-do) • Reviewing vs Design (Technical: How-to-do) • Running vs Development (Operational: Way-to-do) • Questions (activity-centric approach): • On what basis activities/interactions take place? • This refers to perspectives to interact • This refers to actions to take

  6. Designer Programmer Multi-Documentations SSAD Define/Refine Request/Review PRD Conceptual System SCD / DFD Administrator PSD Design/Redesign Review/Revise SDD Arch/Com Technical System Maintainer SOM Develop/Debug WDSC Run/Repeat Operational System Coding / IPE Operator

  7. Multi-Documentations • What are they (document-driven approach)? • PRD – Problem Requirements Document • Conceptual System • PSD – Project Specification Document • Conceptual Techinical • SDD – Software Design Document • Technical system • SOM - Software Operator’s Manual • Technical  Operational • WDSC – Well-Document Source Code • Operational system

  8. Multi-Documentations • Questions (document-driven approach): • What can assist PRD? • What can assist PSD? • What can assist SDD? • What can assist SOM? • What can assist WDSC? CASE Tools???

  9. Auto/Assisted Tools • Computer-Aided SE(CASE Tools): • PRD  DFD / RSP • PSD  Hierarchical DFD • SDD  Architectural Description/Framework • SOM  Natural language/graphical diagram • WDSC Interactive Programming Environment

  10. Case Study: ATS DFD0 • Problem Requirements Document • Introduction • Problem Definition • Product Description (DFD + RSP) • Problem Requirements Document • Introduction • Problem Definition • Product Description SSAD PRD PSD SDD SOM WDSC

  11. Case Study: ATS DFD1-N • Project Specification Document • Introduction • Functional and Data Description • Sub-system (process) Description • Project Specification Document • Introduction • Functional and Data Description • Sub-system (process) Description SSAD PRD PSD SDD SOM WDSC

  12. Case Study: ATS Arch • Software Design Document • Introduction • Data Design • Architectural and Component-level Design • User Interface Design • Software Design Document • Introduction • Data Design • Architectural and Component-level Design • User Interface Design SSAD PRD PSD SDD SOM WDSC

  13. Case Study: ATS re-ADA • Software Design Document • Introduction • Data Design • Architectural and Component-level Design • User Interface Design SSAD PRD PSD SDD SOM WDSC

  14. Streamlining SSAD • Questions?

More Related