PIPT – Mid Point Presentation

Team AmethystAchint Sethi

Gulsharan GorayaSai S Chandrasekharan

Saravanakumar Mariappan

You Imagine. We Create.

Project Overview Team Overview Goals The story so far What was good? Plan for the future Lessons Learnt

April 10, 2023 2Team Amethyst

Client School of Computer Science Point of Contact – Walt Schearer, Associate

Dean for Finance and Administration Business Needs

A standardized tool to be used by all Business Managers for “Planning and tracking financial aspects of activities in research projects”

Mentors John Robert, SEI Mel Rosso-Llopart, ISR


Project RolesTeam Lead, Process Manager – SaiRequirements Manager – AchintClient liaison – GulRisk Manager – SaravanaConfiguration Control Board – Sai, SaravanaArchitecture Board – Sai, SaravanaTechnology Review Board – Achint, Gul

Process RolesScrum Masters – Sai, SaravanaProduct Owners – Gul, Achint


Project goals Improve upon the lessons learnt from our

previous project at SSN Process goals

Use a “project oriented” processStick to the process

Team goalsUse team resources optimallyDeliver the product on time meeting the

scope


Process Project Management Architecture Tasks Data Analysis


Initial thoughtsTo follow an agile processTo take ideas from Scrum, XP

When can we do Scrum? (Lesson Learnt!)When deliverable is CodeWhen we have sufficient domain knowledgeWhen we have a “stable” architectureWhen we have sufficient technology

expertise


Underlying framework – Scrum methodology

Four phases Initiation – 1.5 months

September 1 – October 14 Task driven approach

Stabilization – 2 months October 15 – December 8; 4 sprints

Skill Mastery December 15 – December 31

Implementation January 1 – March 15; 5 sprints


InitiationProject Proposal Sign offMeetings with client – understanding the

business domain Stabilization

15 day iterationsSprint Planning – Sprint goals, tasksExecute TasksStand up meetingsWebsite updateSprint Retrospective


Requirements - Product Backlog Importance Story Estimated story points How to Demo? Built over time by Product Owners

Risks Risk management at beginning of every sprint Loop through ‘Identify, Analyze, Monitor,

Control’ Configuration Management

Configuration Control - baselines


Driven by business drivers and technical drivers

Formal Quality Attributes Elicitation (QAE)

Quality Attributes identified and prioritized by clientQuality Attributes # of critical scenarios

Usability 6

Performance 3

Security 4

Availability 1

Extensibility Not identifiedReference: Amethyst_NFR_v0.1


Technology Drivers

Quality Attributes and Technology drivers led us to arrive at a tiered architecture on top of Eclipse rich client platform

Quality Attribute Focus of investigation

Usability Rich Client Platform

Extensibility High cohesion; Eclipse plug-in architecture

Security Low coupling; Tiered Architecture


April 10, 2023Team Amethyst 13

PIPT Tool

Business Manager Computer

PIPT Tool

Business Manager Laptop

Data

Database server at

SCS

Legend

S/w Component

Contextual Boundary

JDBC Connector

A B A contains B

All images courtesy http://www.hp.com

Principal Investigator Planning Tool

Eclipse Rich Client Platform

Generic Workbench(Perspectives, Editors, Views)

JFaceSWT

Optional Plug-ins

(Help, Update etc.)

Equinox OSGi

Platform Runtime

JVM

OS Key

Layer

Module


Key

<<presentation tier>>

<<plugin>>

<<plugin>>

<<logic tier>>

<<plugin>>

<<data tier>>


<<logic tier>>

<<data tier>>

<<plugin>>

Presentation tier

Logic tier

Data tier

Plug-in

More focus was on -Understanding Business ProcessUnderstanding the entities and data ModelMitigating Technology Risks

Focus on architecture was to understand the critical quality attribute scenarios

Architecture is still being stabilizedArchitecture being integrated with business

process


Task List How much we achieved

Proposal

Product Backlog

Risk Management

Business Process Model

Architecture

Data Model

Eclipse RCP Training

Use case model

High level timeline

Quality Requirements

Configuration Management


Task List How much we achieved

Process Document

Website maintenance

Infrastructure setup – Wiki, IIS, SVN

Technology Feasibility Study

Proof of Concepts

Quality Assurance Plan



Sprint Burn down Analysis

Transparent task allocation Tasks fixed at beginning of every sprint

More responsibleEasy to measure

Mitigated technology risks Creating subject matter experts in –

Technology – GulProcess – SaiRequirements – AchintArchitecture – Saravana


Skill Mastery Phase Individual skill improvementCreate prototypes

Implementation Phase500 story points estimated in backlog ~

1000 hours estimated5 sprints, 4 persons, 72 hours per person

per sprint ~ 1440 hours availableWe know how to deliver in 15 day iteration

cycles


Getting startedNew team

RequirementsDown-scoping took more time than expectedUsed all 4 resources for first few client

meetings Learnt how to conduct effective meetings

Reduced time in meetings over the sprints by time tracking

ProcessGot carried away with AgileLifecycle was good. Intent was wrong.


Knowledge SharingTraining on Process, Eclipse RCP

ArchitectureFocus of our development should have been

more on architectureWe could have explored ACDM as it seems

to be a good choice for our design process Planning and Tracking

Focus was on Sprint specific goals; not on semester goals

Learnt the nuances of “Focus factor” and “Velocity”


SprintsLearnt how to estimate tasks in a sprint

betterLearnt that tasks must be at a micro level in

a sprintSprint retrospective was really helpful

OthersWe do not have a Quality Assurance Plan

defined but we want to go for test driven development during Implementation Phase


QUESTIONS?


Backup Slides

Product OwnersRequirementsClient interactionAct as the bridge between the client and

the team Scrum Masters

Sprint PlanningRisk identification

Task owners


InitiationProject Proposal Sign offMeetings with client – understanding the

business domain Stabilization

15 day iterationsSprint Planning – Sprint goals, tasksExecute TasksStand up meetingsWebsite updateSprint Retrospective


Business Manager

PIPT ToolBusiness Manager

(1 .. n)

Forecasting Data

Forecasts

System External Entity

X Y

Data flows

from X to Y

AdminUser info

DeveloperDashboard design, LD

design

Principal InvestigatorPTA

Information

Business Context


PIPT Tool

PIPT Tool

Business Manager Computer

Business Manager Laptop

Data

Database server at SCS

All images courtesy http://www.hp.com

Legend

S/w Component

Contextual BoundaryJDBC Connector

A B A contains B

PIPT Physical Deployment ViewApril 10, 2023 29Team Amethyst

Legend

S/w Component

Physical Laptop

A B

Business Manager Machine

A contains B

PIPT Client Deployment View


<<device>>Personal

Laptop/Computer

<<component>>Eclipse RCP

<<component>><<library>>

jChart

<<component>><<plugin>>

PIPT

<<device>>Central DB Server

<<component>>MySQL

Key: UML

Node

3rd-Party Component

<<component>>

PIPT Component

<<component>>

PIP Tool Deployment View

Open source libraries

<<component>>


PIPT Client-side Layered View

Principal Investigator Planning Tool

Eclipse Rich Client Platform

Generic Workbench(Perspectives, Editors, Views)

JFaceSWT

Optional Plug-ins

(Help, Update etc.)

jChart Plug-

in

Platform Runtime

JVM

OS Key

Layer

Module



Key


<<plugin>>

<<plugin>>

<<logic tier>>

<<plugin>>

<<data tier>>


<<logic tier>>

<<data tier>>

<<plugin>>

Presentation tier

Logic tier

Data tier

Plug-in


Sprint Burn down Analysis

Follow the chosen approach and methodology and deviate minimally from the objectives and goals of each phase

To follow test driven development and deliver a defect free product

Deliver a working feature every sprint Involve the client during every sprint to

provide feedback Help the users get acquainted with the

new system easily Improve our team skills


Initial thoughts To follow an agile process To take ideas from Scrum, XP

When can we do Scrum? (Lesson Learnt!) When deliverable is Code When we have sufficient domain knowledge When we have a “stable” architecture When we have sufficient technology

expertise We cannot do Scrum until we achieve the

above 4 goals


Project Proposal including – Finalized Scope Process Document Support Processes

Requirements Plan Configuration Management Plan

Schedule Estimated time Timeline for deliverables Deliverables

Roles WBS

Setting up of infrastructure SVN Wiki Project Management Tools – Zoho/ Ace Project Bug tracking system

Requirements Documented as User Stories

The broad level timeline for the development cycle from October to March, will involve mapping the features to the Sprints.


At the end of the semester, during December, we wish to deliver –

SRS in the form of Product Backlog Using requirements elicitation techniques learnt in Managing Software

Development and Methods course High level design diagrams developed for tasks during the sprints

Using knowledge gained in Architecture course Sprint backlog Sprint plans for completed sprints and forthcoming sprint

Using skills learnt in Managing Software Development Test Cases for each of the tasks User feedback for sprint demos Analysis of work done in terms of overall estimated velocity and actual

velocity Burn down charts for each sprint will be provided Time sheets of each team member Leveraging skills learnt in Measurements and Managing Software Development

course. Working features developed at end of each sprint


At the end of March, the additional deliverables will be – Final product – which will consolidate all the

features already delivered during the sprints and shown as a demo of all the features

User guide Product Technical documentation


PIPT – Mid Point Presentation

Business

Transcript of PIPT – Mid Point Presentation