J2WS (Java 2 Web Services)
a service standard for implementing applications and services in Java
overarching philosophy and guidelines for developing software in an unknown, rapidly changing environment. meant to be used with a specific development methodology (like UP).
4 basic values/priorities:
(1) responding to change over following a plan
(2) individuals and interactions over processes and tools
(3) working software over comprehensive documentation
(4) customer collaboration over contract negotiation
Two types: release or sprint. A running estimate of work left in the sprint or left before ready to release
COM+ (Component Object Model Plus)
a standard for software component connection and interaction developed by Microsoft
CORBA (Common Object Request Broker Architecture)
a standard for software component connection and interaction developed by the Object Management Group (OMG)
every day during a sprint, this short (15 min max) meeting is held. members answer 3 questions:
(1)what have you done since the last meeting?
(2)what will you do by the next meeting?
(3)what is preventing you from finishing your work?
JavaBeans that can execute on a server and communicate with clients and other components using CORBA
Extreme Programming (XP)
an adaptive, agile development methodology taking best practices to their most intense level. 4 core values:
(1)communication-projects fail without it
(3)feedback-frequent, meaningful feedback
(4)courage-don't be afraid to stand up to the schedule if it's too tight. "Do it right."
a Microsoft service standard based on SOAP
Model Driven Architecture (MDA)
an OMG initiative that is built on the principles of abstraction, modeling, reuse, and patterns to provide companies with an additional tool to help them understand and extend their enterprise-level systems; provides a framework to identify and classify all the system development work being done in an enterprise
a set of classes that are designed to be reused in a variety of programs
a prioritized list of user requirements used to choose work to be done during a Scrum project
the client stakeholder for whom a system is being built who maintains the backlog
An adaptive development methodology based on responding to situations as rapidly and positively as possible. Heavy use of product backlog to control project.
3 main organizational elements: product owner, scrum master, scrum team.
Uses sprints, or a timebox with a specific deliverable goal
the person in charge of a Scrum project, similar to a project manager; enforcer of rules that helps team complete work
the team members working on a Scrum project, typically 5-9 developers
Simple Object Access Protocol (SOAP)
a standard for component communication over the Internet using HTTP and XML
a time-controlled miniproject that implements a specific portion of a system
a principle setting the time for each element--each product is a series of releases made up of the following elements: Sprint Planning Meeting, Sprint, Daily Scrum, Sprint Review, Sprint Retrospective
the standard object-oriented system development methodology with 4 phases: inception, elaboration, construction, and transition.
represent functionality that will be valued by users (typically functional requirements). Three C's: card (written description), conversation (to flesh it out), confirmation (tests to document story and verify completion).