Catbert Presentation

1
Catbert Presentation

• Aug 9, 2007
• Hyeeun You

2
Agenda

• Overview
• Requirements
• Process
• Design
• Lessons Learned
• Fall semester plan
• Questions

3
Agenda

• Overview
• Project Introduction
• Stakeholders
• Requirements
• Process
• Design
• Lessons Learned
• Fall semester plan
• Questions

4
Project Introduction

• MSE projects have a central storage for their
  artifacts Dogbert
• MSIT projects also need a central web storage
  Catbert!
• To track MSIT practicum activation status
• To store, manage, and display MSIT projects
• Nature of MSIT practicum
• Conducted both on campus and at distance
• Within two semesters
• 1-4 person teams (usually 2 people)

5
Stakeholders

• Client
• Mel-Rosso Llopart
• Team
• Hyeeun You
• Mentor
• Anthony J. Lattanze
• Other stakeholders
• System manager (Edward Walter)
• Catbert users (MSIT students, Catbert admins,
  mentors, technical advisors, clients)

6
Agenda

• Overview
• Requirements
• Functional requirements
• Quality attributes and Constraints
• Context
• Process
• Design
• Lessons Learned
• Fall semester plan
• Questions

7
Functional requirements

• Key functional requirements
• 1. Activate practicum
• 2. Manage activation status of practicum
• 3. Manage MSIT practicum artifacts
• 4. Search certain information about practicum
• 5. Display public information of practicum

8
Quality attributes and Constraints

• Quality attributes
• Usability
• Availability
• Reliability
• Security
• Performance
• Constraints
• Business 2 semesters to develop product
• Technical must be web-based

9
Context

• Context diagram about Catbert users

Catbert administrator
Catbert
10
Context

• Context diagram about Catbert users

Catbert administrator
Practicum activation status
Catbert
11
Context

• Context diagram about Catbert users

Catbert administrator
Practicum activation status
MSIT students
Catbert
12
Context

• Context diagram about Catbert users

Catbert administrator
Practicum activation status
MSIT students
Catbert
Practicum activation data, project artifacts
13
Context

• Context diagram about Catbert users

Catbert administrator
Practicum activation status
Practicum activation status
MSIT students
Catbert
Practicum activation data, project artifacts
14
Context

• Context diagram about Catbert users

Catbert administrator
Practicum activation status
Practicum activation status
Practicum activation status, project artifacts
MSIT students
Mentors, Technical advisors
Catbert
Practicum activation status, project artifacts
Practicum activation data, project artifacts
15
Context

• Context diagram about Catbert users

Catbert administrator
Practicum activation status
Practicum activation status
Practicum activation status, project artifacts
MSIT students
Mentors, Technical advisors
Catbert
Practicum activation status, project artifacts
Practicum activation data, project artifacts
Public project artifacts
Clients, World
16
Agenda

• Overview
• Requirements
• Process
• Design
• Lessons Learned
• Fall semester plan
• Questions

17
Process

• Scrum
• Why Scrum?
• One-person development team, 2 semesters -gt
  Lightweight Agile
• Familiarity, web application system -gt Scrum!
• However, Scrum doesnt have any guide for
  gathering requirements and creating architecture.
• Plan for this semester
• Requirements gathering requirement analysis -gt
  architecture design
• Requirements
• Created Use Cases and Quality Attribute
  Scenarios
• Architecture
• Met with system manager to learn about Dogbert
  architecture
• Submitted draft of architecture document to
  client for review
• Currently revising architecture and analyzing
  tradeoffs
• Preparing for next semester
• Creating Product Backlog -gt Prioritize the tasks
  in the Product Backlog

18
Agenda

• Overview
• Requirements
• Process
• Design
• High level architecture CC View
• High level architecture Module View
• Tradeoffs
• Project Risks
• Lessons Learned
• Fall semester plan
• Questions

19
High level architecture CC View
Authenticate Entity
LoginView
LoginController
ActivateView
ActivateController
Activation Status Entity
Client Browser
ProjectView
ProjectController
UploadView
UploadController
Practicum Artifacts Entity
SearchView
SearchController
Legend
Call-Return
Data Access
Client component
View component
Controller component
Model component
Http(s)
20
High level architecture Module View
LoginController
LoginPage
ActivatePage
ActivateController
ProjectPage
ProjectController
UploadPage
UploadController
SearchPage
SearchController
Catbert
Legend
Uses
Module
21
Tradeoffs

• Separate controllers vs. single view/controller
  component
• Separate controllers Security
• Single view/controller component Performance
• Authentication with SCS authentication data vs.
  Catbert authentication data
• SCS authentication data Cost
• Catbert authentication data Usability
• Searching criteria
• WEB-DAV
• Web pages

22
Project Risks
23
Agenda

• Overview
• Requirements
• Process
• Design
• Lessons Learned
• Fall semester plan
• Questions

24
Lessons Learned

• Requirements should be refined with client
  iteratively and through various ways
• Schedule should be anticipated and estimated from
  the early beginning
• Stakeholders schedule
• Unexpected occurs
• Structured process for architecture is required

25
Agenda

• Overview
• Requirements
• Process
• Design
• Lessons Learned
• Fall semester plan
• Questions

26
Fall Semester Plan

• Perform estimation
• Set scope
• Revise Product backlog
• Scrum agile, modular development
• Three Sprints (September, October, November)
• Add sprint backlog items to 30-day schedule
• Implementation
• Testing
• Deliver code

27
Questions
28
Process
Proposal
Feedback
Feedback
Gathering information
Feedback
SRS draft
Feedback
SAD draft
Feedback