Project Analysis Course (2012-2013) Course Overview Project ideas Presentation.

Slides:



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

Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
MIS 3504 Digital Design and Innovation Week 11 Photo: Installation by Jenny Holzer, US Pavillion, Venice Biennale 1990.
Iterate (Requirements, Design) IMD07101: Introduction to Human Computer Interaction Brian Davison and Tom McEwan 2011/12.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
SWE Introduction to Software Engineering
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Identifying needs and establishing requirements Chapter 7a.
Identifying needs and establishing requirements Chapter 7b.
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
Requirements Management Course Plan System Group Company – Training Department By: Dr. Ahmad Abdollahzadeh.
M.Sc Projects David Wilson M.Sc Projects Coordinator for Computing & Information Systems.
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
7M822 Software Requirements Introduction 7 September 2010.
1 College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 2 Chapter 6 & 7 System.
Business and Management Research
Business and Management Research WELCOME. Business and Management Research Instructor:Rawaa Muhandes Office Number: 624 Term/yearSemester.
Project Analysis Course ( ) Week 2 Activities.
Project Analysis Course ( ) Final Project Report Overview Prepared by: Sijali Petro Korojelo (Course Assistant)
Introduction to SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2009.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Object-Oriented System Analysis and Design Chapter III- Requirement Elicitation Collecting and organizing users requirement- WHAT- User needs.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 22 – 10 – 2011 College Of Computer Science and Information, Information Systems.
Software engineering lec4 Requirements. Developing requirements Start thinking about particular problem Understand the problem  Domain analysis Gather.
Chapter 5: Requirement Engineering Process Omar Meqdadi SE 2730 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
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)
Slide 10A.1 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005.
Project Analysis Course ( ) Project Case - Ideas Prepared by: Sijali Petro Korojelo- Course Assistant.
Requirements Engineering Requirements Elicitation Process Lecture-9.
Lecture 7: Requirements Engineering
Sprint (2) Deliverables Capstone Courses. What are Sprint (2) Deliverables ? 1.Revised High level planning and scheduling WBS and Gannt (with risk assessment).
CT1404 Lecture 2 Requirement Engineering 1 1. Today's Lecture Definition of a Software Requirement Definition of Software Requirements Management Characteristics.
Analysis Modeling CpSc 372: Introduction to Software Engineering
Identifying needs and establishing requirements Data gathering for requirements.
INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 2: Gathering System Requirements Instructions.
Software project management (intro)
CS4042 / CS4032 – Directed Study 28/01/2009 Digital Media Design Music and Performance Technology Jim Buckley Directed Study (CS4042.
Project Analysis Course ( ) Course Overview.
Requirements Engineering Process
Identifying Needs and Establishing Requirements Presenters: Veronica Gasca Jennifer Rhough.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Now what? 1.  I have short-listed projects I am interested in  I know the types of projects I would like to pursue  I have an idea of the resources.
Lecture 4/2/16. Learning Objective Establishing requirements Define requirements Requirements discovery vs requirements gathering Classifying Requirements.
1 Systems Analysis & Design 7 th Edition Chapter 2.
Requirements Elicitation Hans Van Vliet, Software Engineering: Principles and Practices, 3rd edition, Wiley (Chapter 3) 1.
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
Software engineering lec3 Requirements. Contents Developing Requirements Domain analysis The starting point for software projects Defining the problem.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
GATHERING DATA Supplementary Note. What are requirements? A requirement is a statement about an intended product that specifies what it should do or how.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
Requirements Management with Use Cases Module 0: About this course Requirements Management with Use Cases Module 0: About this course.
1 Requirements Elicitation – 2 Lecture # Requirements Engineering Process Requirements Elicitation Requirements Analysis and Negotiation Requirements.
1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.
Investigating System Requirements
SNS College of Engineering Coimbatore
Business and Management Research
CIS 210 Systems Analysis and Development
Project Analysis Course
Chapter 7 Determining System Requirements
Overview Characteristics for gathering requirements.
Requirement Engineer Terms and Conditions
Joint Application Development (JAD)
Systems Analysis Project
Put the Lesson Title Here
Presentation transcript:

Project Analysis Course ( ) Course Overview Project ideas Presentation

 student in groups, chooses a project case to develop  The group then:  Read on the case  finds requirements for the project case  analyzes the requirements  Specifies & models the requirements to design a system  and lastly, presents final results. Recap (yesterday’s lecture)- Project Aims:

Suggested Focus Areas: 1.E-commerce System 2. Online Examination System 3. Online Voting 4. Document Management System 5. Online Student Information System

Other Focus Areas:  Social Networks (Online Chats)  Reservation Systems (Hotel, Planes, etc.)  Housing Systems (finding/renting houses)  Banking Systems  …..?? What ever you choose!! As long, not too simple, I am

week one: Project Environment Understandability(June 3-7)

Overview:  Presentation format- PowerPoint slides  Presentation Length – 6 to 9 Slides  Presentation Time- 10 min  Please remember to bring handouts for presentation session Project Idea Presentations: (presentations format)

First Slide: Include:  UvA logo:  Course Name – Project analysis 2012/2013  THE PRESENTATION SERIES - First Week- Project Idea Presentation  Project Title e.g. XXX Document Management System YYY Student Information System  Group Members List e.g. 1. Hodjat Soleimani Reg #: Sijali Krojelo Reg #: ….

Middle Slides:  Introduction (1 Slide)  Project Description(2-3 Slides)  Elicitation Techniques (1-2 Slides)  Project Schedule (1 Slide)

Middle Slides……  Introduction (1 Slide) Short intro on the area you are working on If E-commerce then:  What is e-commerce?  What is it about?  Advantages of e commerce

Middle Slides:  Project Description(2-3 Slides) Short description of your project. Focus on:  project goal (what is it about?)  What will designed system do?  The chosen scope of work based on selected scenarios  Stakeholders and intended users  List of expected Functional (deliverable service) and non-functional (constraints) requirements  Context Diagram ver 1.0

Middle Slides:  Elicitation Techniques (1-2 Slides) Very short discussion on techniques you will use to gathering requirements?  Brainstorming?  Existing systems?  Interview?  Observation?  Document review?  JAD?  Prototyping?  Use case scenarios?  Questionnaires?

Project Schedule:  1 - Slide showing work plan- for the whole project work  2- The excepted roles of group members (requirements engineer, Domain expert, End-user, …)

Project Literature:  Search materials on internet on the project, sample sites:

Any Questions?