Transcript Distributed Software Development

NOTICE!
• These materials are prepared only for the students enrolled in
the course Distributed Software Development (DSD) at the
Department of Computer Science and Engineering,
University of Mälardalen, Västerås, Sweden and at the Faculty
of Electrical Engineering and Computing, University of Zagreb,
Croatia (year 2010/2011).
• For all other purposes, authors’ written permission is needed!
• The purpose of these materials is to help students in better
understanding of lectures in DSD and not their replacement!
2016-04-10
1
Distributed Software Development
2016-04-10
2
Toni Pivčević
Transport4you – Alpha prototype
2016-04-10
3
Important events
• initial contact with customer
– changes to requirements definition document
• addition of unsuccessfull usecases
• further elaboration of current requirements
– identification of system boundaries
• new member
• project leader role change
– lack of interest, commitment
2016-04-10
4
Development Methodology / Scrum
• artifacts:
– product backlog
– sprint backlog
– sprint backboard
• shared on google docs
2016-04-10
5
Current project state
• requirements/use-cases “mature”
• system arhitecture highly elaborated
• highly modularized / decoupled
– project,package,file,method...
• development process
– iterative
– architecture-centric
– risk-centric
2016-04-10
6
Implemented functionality (1)
• TransportUnit project
– event handling
– threading
– smart detection
• TransportModel project
– java classes
– JPA annotation (@Entity...)
– ant task exportSchema
– transportNetwork.xml  DB
2016-04-10
7
Implemented functionality (2)
• TransportCommunicationProtocol project
– TMA-TUA communication
– server/client
• TCP/IP
• GPRS
– threading
• TransportWeb project
– user registration
– login
2016-04-10
8
Implemented functionality (3)
• technical services
– logging
– preliminary ant build files
– testing
2016-04-10
9
Statistics (1)
• work hours
2016-04-10
10
Statistics (2)
• SVN repository
– 7 projects
– 82 *.java files
– commit activity
2016-04-10
11
Experiences & Risks
• communication
– excellent project-team leader communication
– lack of communication with other members
• lack of experience
• work load
– relatively balanced (could be better)
• scrum artifact usage
2016-04-10
12
Demo (1)
• TUA sim video
• TM sim video
2016-04-10
13
Demo (2)
• web application screenshots
2016-04-10
14
Questions
2016-04-10
15