Project Analysis Course (2011-2012) Final Project Report Overview Prepared by: Sijali Petro Korojelo (Course Assistant)

Slides:



Advertisements
Similar presentations
Project Analysis Course ( ) Final Project Report Overview.
Advertisements

WEBQUEST Let’s Begin TITLE AUTHOR:. Let’s continue Return Home Introduction Task Process Conclusion Evaluation Teacher Page Credits Introduction This.
Advanced Technical Writing Lecture 2 Progress report.
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Karolina Muszyńska Based on:
Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
WEBQUEST Let’s Begin TITLE AUTHOR:. Let’s continue Return Home Introduction Task Process Conclusion Evaluation Teacher Page Credits This document should.
Documenting Requirements using Use Case Diagrams
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
1 Spring 2007 CSCI 660 CSCI-660 Project Title Project team members’ names.
Technical Communication 1
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
Chapter 7: The Object-Oriented Approach to Requirements
USE Case Model.
Chapter 7 Report writing
The Chicago Guide to Writing about Multivariate Analysis, 2 nd edition. Paper versus speech versus poster: Different formats for communicating research.
GUIDELINES FOR PREPARATION OF PROJECT REPORT Ramesh Parajuli.
RUP Requirements RUP Artifacts and Deliverables
Project Analysis Course ( ) Week 2 Activities.
Object-Oriented Analysis - Instructor Notes
SYS466: Analysis and Design Using OO Models
Systems Analysis and Design in a Changing World, 6th Edition
Put the Title of the WebQuest Here A WebQuest for xth Grade (Put Subject Here) Designed by (Put Your Name Here) Put Your Address Here Put some interesting.
Put the Lesson Title Here A webquest for xth grade Designed by Put your You may include graphics, a movie, or sound to any of the slides. Introduction.
Project Analysis Course ( ) Project ideas Presentation Prepared by: Sijali Petro Korojelo (Course Assistant)
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
G050: Lecture 02 Evaluating Interactive Multimedia Products
10/10/2015 IENG 471 Facilities Planning 1 IENG Lecture END Project Report Requirements & Project Presentation Information.
Chapter 6 Use Cases. Use Cases: –Text stories Some “actor” using system to achieve a goal –Used to discover and record requirements –Serve as input to.
Project Analysis Course ( ) Course Overview Project ideas Presentation.
Faculty of Computer & Information
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 4: Restaurant.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Report Rough Draft Components Project 1, Fall 2008 The information in this PPT is intended to aid the group member assigned to write the rough draft Slides.
Lesson Planning: part # 1 Lecture # 7. Review of Lesson # 6 We talked about the following elements of Presentation, Practice and Production stages of.
Going Deeper with Mark Twain A WebQuest for 10th Grade Composition Designed by Sandy Schaufelberger Wes-Del High School, Gaston IN
Introduction To Engineering Bike Lab 1 – 4 Report Agenda: Lab Report Format Team Writing Outline Lab 1 Report.
System sequence diagrams
Analysis Modeling CpSc 372: Introduction to Software Engineering
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 5 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH CHAPTER.
INFO275 Database Management Term Project. Overview Your project will be to define, design and build a functioning database, to support an application.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 2: Gathering System Requirements Instructions.
UML - Development Process 1 Software Development Process Using UML.
Technical Report Outline Title Page Frontispiece Abstract Table of Contents List of Figures/ List of Tables.
Copyright © 2007, Oracle. All rights reserved. Managing Items and Item Catalogs.
INFORMATION X INFO415: Systems Analysis.
“Copyright and Terms of Service Copyright © Texas Education Agency. The materials found on this website are copyrighted © and trademarked ™ as the property.
Project Report Format for Final Year Engineering Students.
Pepper modifying Sommerville's Book slides
Systems Analysis and Design in a Changing World, 6th Edition
Seminar Report Structure ARRANGEMENT OF CONTENTS
System sequence diagrams
Week 10: Object Modeling (1)Use Case Model
UML Use Case Diagrams.
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design in a Changing World, 6th Edition
Project Analysis Course
Writing reports Wrea Mohammed
Sample Title for a W. P. Carey Presentation
Welcome 1 This is a document to explains the chosen concept to the animator. This will take you through a 5 section process to provide the necessary details.
Course Name: Special Problems (SPCL 101)
Graduation Project Project Name
Put the Lesson Title Here
TECHNICAL REPORTS WRITING
Presentation transcript:

Project Analysis Course ( ) Final Project Report Overview Prepared by: Sijali Petro Korojelo (Course Assistant)

Report Content Project Analysis Course ( ) Final Report Overview Prepared by: Sijali Petro Korojelo (Course Assistant)

Project Report Cover Prepared by: Sijali Petro Korojelo (Course Assistant) Project Analysis Course ( ) Final Report Overview

Table of Content Page (structure) Prepared by: Sijali Petro Korojelo (Course Assistant) Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  1. Introduction Start with the discussion of the general area you are working on i.e. inventory management, business dashboard, reservation systems, etc. General overview of what is the area about? Recall report 1 Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  1.1 Project Description Detailed description of your specific project Recall first week report on project description, and the scenario of the third week report Extract from the two a good project description Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  1.2 Project Goal Detailed description of the goal of your project. Recall first week report. The goal should be precisely stated… e.g. The project aims at developing a dynamic web based system that will keep track of customer information and sales……… ……………… Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  1.3 Project Scope The projects you are doing are very extensive generally, here provide explanation of the scope of your project o what exactly will you be able to cover in the project and what will you not cover o Scope may also include which steps of system development will you cover and what will you not cover ( i.e. requirement, specification and modelling, but not implementation) Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  1.4 Intended Users Provide descriptions of the users of the system Recall week 1 and 2 reports, to extract user information Do not go into details on what each user will do, just provide a brief explanation of the users roles Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  2. Requirement Elicitation & Analysis Here start with the brief description of what is this section is about Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  2.1 Requirement Gathering Provide explanation of the requirement gathering techniques you used in your project For each identified technique, show how the technique was used Recall report 1 and 2 for the techniques Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  2.2 Requirement Analysis Start this section by providing a description of the requirement analysis technique(s) you followed in your project Note only saying we followed this technique (e.g. OOP, Agile), but what steps you followed in the process. Recall week 1 and 2 reports Note that the explanation should not be few sentences Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  Functional Requirements Provide the description of all functional requirements of the system Recall week 2 report They should be well organized and structured Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  Non Functional Requirements Provide the description of all the non functional requirements of the system Recall week 2 report They should also be well organized and structured Note: requirements might have changed in the process and hence next section you will describe the new generated requirements Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  2.3 Revised Requirement Analysis Results In this section provide a description of the new modified requirement, generated from the first requirements (after prioritization) You should discuss both revised functional & non functional requirements These revised requirements are the ones used in system modelling Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  2.4 Requirement Validation Here discuss the approaches you used in validating your requirements You should not focus only on which approaches you used, but what processes were involved in each approach Recall class lecture on validation Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  2.5 Use Case Modelling Start this section providing explanation on the main actors of the system and their roles, and the scenario for the whole use case (in section 2.5.1) Recall week 2 report Project Analysis Course ( ) Final Report Overview

Prepared by: Sijali Petro Korojelo (Course Assistant)  Use Case Diagram Provide UCD Project Analysis Course ( ) Final Report Overview  Use Case Description Provide descriptions of 4-5 sample use cases Description should be in tabular format should contain:  Use case name  Actors  Pre conditions  Post conditions  Main flow of events  Alternative flow of events

Prepared by: Sijali Petro Korojelo (Course Assistant)  3. Information System Design Provide a short description of the aim of this section which is, designing class and interaction diagram Project Analysis Course ( ) Final Report Overview  3.1 Classes & Class Diagram Start by identifying the classes and attributes (can be in tabular format) Then provide the class diagram Recall week 3 report

Prepared by: Sijali Petro Korojelo (Course Assistant) Project Analysis Course ( ) Final Report Overview  3.2 System Interaction Diagrams Start by a short introduction on what this section is about Provide the full description of the sequence(s) diagram + the sketch(s) Provide description of activity diagram(s) / state diagram(s) + the sketch(s)

Prepared by: Sijali Petro Korojelo (Course Assistant) Project Analysis Course ( ) Final Report Overview  4. Conclusion & Future work Conclude your work by summarizing what you did in the project, what lessons you learned Provide a short description of the future remaining work  5. References Provide a list of references you used in your work

Prepared by: Sijali Petro Korojelo (Course Assistant) Project Analysis Course ( ) Final Report Overview  Report Length Should be Pages Use Arial / Times new roman fonts (size 12). Use justification property in the text. Spacing between text should be 1.15 Generate auto- table of content (define headings & subheading) Main sections should start in a new page (i.e. sections 1, 2, 3, 4, 5, …..) Sub sections should not start in new pages (i.e. 1.1,..3.1, ….)

Any Questions? Prepared by: Sijali Petro Korojelo (Course Assistant)