CIS 4910 Information Systems Development Project Project Documentation.

Slides:



Advertisements
Similar presentations
Unit Testing in the OO Context(Chapter 19-Roger P)
Advertisements

SYSTEM PROGRAMMING & SYSTEM ADMINISTRATION
ISBN Chapter 3 Describing Syntax and Semantics.
July 11 th, 2005 Software Engineering with Reusable Components RiSE’s Seminars Sametinger’s book :: Chapters 16, 17 and 18 Fred Durão.
Use-case Modeling.
COSC 120 Computer Programming
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Bina Nusantara 7 C H A P T E R MODELING SYSTEM REQUIREMENTS WITH USE CASES.
Describing Syntax and Semantics
COBOL for the 21 st Century Stern, Stern, Ley Chapter 1 INTRODUCTION TO STRUCTURED PROGRAM DESIGN IN COBOL.
1 A Student Guide to Object- Orientated Development Chapter 9 Design.
1. 2 Chapter 1 Introduction to Computers, Programs, and Java.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Domain-Specific Software Engineering Alex Adamec.
System Implementation
Documentation 1. User Documentation 2. Technical Documentation 3. Program Documentation.
The chapter will address the following questions:
1 Introduction to UML DIAGRAMS & CLASS DIAGRAM Chapter 7,8 主講人 : 許勝杰
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Structured COBOL Programming, Stern & Stern, 9th edition
PHASE 4 SYSTEMS IMPLEMENTATION Application Development SYSTEMS ANALYSIS & DESIGN.
RUP Fundamentals - Instructor Notes
Software Requirements Engineering CSE 305 Lecture-2.
1 Chapter 13 Understanding Computers, 11 th Edition 13 Program Development and Programming Languages TODAY AND TOMORROW 11 th Edition CHAPTER.
Chapter 1 Introduction to Structured Design. Introduction  System  A combination of people, equipment, and procedures that work together to perform.
Approaching a Problem Where do we start? How do we proceed?
SE: CHAPTER 7 Writing The Program
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
1 CS Tutorial 5 Frid. Oct 23, 2009 Design Document Tutorial.
TAL7011 – Lecture 4 UML for Architecture Modeling.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Lecture 1: Introduction – Graduation Projects Topics to Discuss in Lectures 1. Project Deliverables 2. Course grading 3. Project Concept Writing.
Use Case Model Use case description.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Chapter 1: Introduction to Visual Basic.NET: Background and Perspective Visual Basic.NET Programming: From Problem Analysis to Program Design.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
Alexandria University Faculty of Science Computer Science Department Introduction to Programming C++
William H. Bowers – Specification Techniques Torres 17.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Learning Objectives Today we will Learn: The different methods of implementation The differences between user and technical documentation.
Systems Analysis and Design in a Changing World, Fourth Edition
Introduction to OOAD and UML
UML Diagrams By Daniel Damaris Novarianto S..
Document Development Cycle
Chapter 1: Introduction to Systems Analysis and Design
Modern Systems Analysis and Design Third Edition
Unit 17 System Implementation
Group Y Presenters: (indicate roles)
Object-Oriented Analysis and Design
Architecture Concept Documents
Systems Analysis and Design With UML 2
Unified Modeling Language
System Design.
UML Diagrams Jung Woo.
Chapter 4 Computer Software.
Unified Modeling Language
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Chapter 1 Introduction(1.1)
Analysis models and design models
SYSTEMS ANALYSIS & DESIGN
Chapter 1: Introduction to Systems Analysis and Design
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

CIS 4910 Information Systems Development Project Project Documentation

Overview Systems Manual User Manual Design Specifications Manual

Systems Manual What is a systems manual? Provides information about the implementation of the system Aid in installation of your software or modification of your software Contains two parts: Getting the software to run on a given system Gives the programmer enough information to be able to modify the software intelligently What does the systems manual contain?

Systems Manual Contents of the Systems Manual: Introduction Installation A Guided Tour

Systems Manual Systems Manual Outline: I. Introduction II. Installation A. Hardware and Software Requirements B. Loading the Software C. Building the Software D. Installing the Software E. Documentation F. Known Deficiencies III.A Guided Tour A. Organization of the Source B. High-level architecture C. High-level Walk Through D. Know Problems

Systems Manual Installation: Describes how to install your system on a given platform Hardware/software requirements to build & run the software (compilers, operating systems, supporting systems, devices) How to load the source onto the new machine How to make software ready for general use Description of user documentation (What it is, where it is located) Miscellaneous (Description of known bugs and inconsistencies, problems likely to occur, work arounds)

Systems Manual Guided Tour A concrete, high-level view of the implementation of your system Includes how the software is constructed, what the important data structures are (a feel for how program works)

Systems Manual Guided Tour (cont) Contents: Organization of the source files, which indicates the relationship of the files and how they are grouped Ex. User interface modules are the html files High-level architecture Shows the overall structure of the system High-level walkthrough Take the programmer through the sequence of events that occur during the execution of your program (basic flow of control and data through the entire system) Porting hints Identify issues that should be addressed when porting to a new machine Known problems Identify the known bugs, inconsistencies, or other problems

User Manual What is a User Manual? Explains what to do with the product and how to do it

User Manual What are the tasks for the writer of a user manual? Explain the interface (what the user will see) Explain the overall premise of the product Explain the basic interface functions (menus, windows, toolbars, etc.) Give a few varying examples of how to use the product Each option of the system should be explained (all error messages should be explained also)

User Manual Hints in writing: Consistency Naming techniques Abbreviations

User Manual Hints in writing: (cont) Write in bite-sized chunks: Forces writer to write clear statements with less rambling Keeps the reader reading longer Use lots of headings and subheadings Grammar & Style Spelling Proper word usage Punctuation

User Manual Contents of the User Manual: Introduction Installation Instructions and Requirements Guided Tour Walk Through Each Scenario

Design Specifications Manual What is a design specifications manual? Provides a detailed specification of the system What does the Design Specifications Manual contain?

Design Specifications Manual Contents of the Design Specifications Manual: Table of contents Chapter 1: Introduction Chapter 2: Design Overview Chapter 3: Static Model Chapter 4: Dynamic Model Chapter 5: Data Model Chapter 6: Functional Testing Glossary

Design Specifications Manual Chapter 1: Introduction Problem Statement and Purpose of the system Chapter 2: Design Overview Context Diagram Use case diagram Chapter 3: Static Model Describes the collection of classes created to model the system Class diagrams Chapter 4: Dynamic Model Describe each activity that is performed in the system Collaboration diagrams Ex. Four unique scenarios for each stakeholder (each scenario has at least 4 screens)

Design Specifications Manual Chapter 5: Data Model Depicts all the relationships of data usage in the system E-R Diagram Level 1 E-R Diagram Level 2 Entity Maps Sample Data Data Dictionary Chapter 6: Functional Testing Describes how to test the system Watir Test Scripts Ex. One for each Collaboration Diagram Glossary Relevant terms & Abbreviations explained