AD description template definition Marián Mlynarovič FIIT Lectures 2006.

Slides:



Advertisements
Similar presentations
Scope of TOGAF ADM The scope of the four architecture domains of TOGAF align very well with the first four rows of the Zachman Framework, as shown in the.
Advertisements

Systems Analysis and Design in a Changing World
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
<<Date>><<SDLC Phase>>
Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC) [Insert Project Name] Post Implementation Review (PIR) [Insert Date of PIR] [Insert.
CS 411W - Notes Product Development Documentation.
ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.
Post Implementation Review (PIR) [Insert Date of PIR]
Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC) [Insert Project Name] Preliminary Design Review (PDR) [Insert Date of PDR] [Insert.
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
Slide 1 Software Design Document. Slide Introduction 2.0 System Architecture Description 2.1 System Architecture 2.2 Database Components 2.3 GUI.
Software Engineering COMP 201
PROPOSALS and PERSUASION A Guide for Creating Effective Proposals Based on Anderson, Paul V. Technical Writing: A Reader-Centered Approach, 5 th ed
WKES 3202 SOFTWARE REQUIREMENTS ENGINEERING SEMESTER 1 SESSION 2004/2005.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
A summary of the PSS-05 URD template
Designing Your Project Output Achieving your objectives by targeting your audience Ken Peffers UNLV February 2004.
Software engineering Olli Alm Lecture 2: requirements, modelling & representation.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
Requirements Engineering
[Insert Project Name] Preliminary Design Review (PDR) [Insert Date of PDR] Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC)
Chapter 11 Proposals, Business Plans, and Special Reports 11.
Documenting Network Design
What are the key improvements in web content management?
Developing Enterprise Architecture
[Insert Project Name] Architecture Review [Insert Date of AR] Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC)
Project Analysis Course ( ) Final Project Report Overview Prepared by: Sijali Petro Korojelo (Course Assistant)
IHE Supply white paper Process for cross-domain case capture and analysis.
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
Enterprise Product Implementation Process. Components of a Successful Implementation  A detailed Scope Document for customer review and signoff  Creation.
U.S. Department of Agriculture eGovernment Program Select Level Business Cases Overview of Business Case Sections.
Software Requirements Engineering CSE 305 Lecture-2.
Emerging Technologies Work Group Master Data Management (MDM) in the Public Sector Don Hoag Manager.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Lecture 7: Requirements Engineering
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
6/3/2016 IENG 471 Facilities Planning 1 IENG 465 – Final Design Project Report & Presentation Requirements.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
Requirement Handling
I Copyright © 2007, Oracle. All rights reserved. Module i: Siebel 8.0 Essentials Training Siebel 8.0 Essentials.
BCIS 4610 Project - Interim Report 1 BCIS 4610 INTERIM REPORT By : Name 1, Name 2 and Name 3. LLC.
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
Project Demonstration Template Computer Science University of Birmingham.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Architecture & Cybersecurity – Module 3 ELO-100Identify the features of virtualization. (Figure 3) ELO-060Identify the different components of a cloud.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Developing a High-Level Design Final Design and Implementation.
2/27/2016 IENG 471 Facilities Planning 1 IENG 464 – Conceptual Design Project Report & Presentation Requirements.
SDLS Protocol Green Book initiation Ignacio Aguilar Sanchez (ESA) CCSDS Spring Meeting 2010 | Portsmouth, VA.
CSE Senior Design I Architecture Design Review/Final Exam Template CSE 4316 Final Exam.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Preparing & Evaluating RFPs The PMO Role Kim Brain Senior Project Manager, Brain Works Consulting, LLC.
1 Statements of Work – Getting Them Right!!. 2 Today’s Agenda A.The Basics B. Sources of Information C. Scenario #1: Procurement is in the loop D. Scenario.
Primer Subbu Allamaraju BEA Systems Inc WSRP F2F Meeting, May 2006.
VA Internal Use Only 1 Product Architecture Recommendation Briefing Template.
Principal Investigator ESTCP Selection Meeting
Principal Investigator ESTCP Selection Meeting
SDLS Protocol Green Book initiation
Object-Oriented Design
Project 1: System Concept
IPMA Portal Presentation
ภาควิชาวิทยาการคอมพิวเตอร์ คณะวิทยาศาสตร์
Software Requirements Specification (SRS) Template.
Principal Investigator ESTCP Selection Meeting
Requirements Document
Strategy.
Principal Investigator ESTCP Selection Meeting
Title: select a descriptive title
Presentation transcript:

AD description template definition Marián Mlynarovič FIIT Lectures 2006

AD section definition Document control –Identifies version Table of contents –Word processing facilities Introduction and management summary –Describing the objectives of the AD –Summarizing the goals of the system described –Summarizing the scope a key system requirements –Presenting high-level overview of the solution The benefits of the solution, the risks in implementation

AD section definition Scope definition –The broad functional areas to be provided by the system –The external interfaces of the system and the external systems that communicate via these interfaces –Any system to be decommissioned and modified –Any data to be migrated into the system Overview of requirement and concerns –Business drivers: motivation for the solution “enabling the better cutomer service via web portal” –Goals: Present briefly business and technology goals “ reduce cost per transaction by 15%” –Functional requirements –Required quality properties Performance, availability, security, scalability,..

AD section definition Views –For each of view (for Example functional view) View specific architectural principles with rationale and implications. Each principle should be numbered and whether possible to tied back to previous principle (previous view) View model (s). Present the model that make up view Standards Applied quality attributes to the view Quality property summary Important scenarios –Demonstrate the key functionality of system Appendices