Development Lifecycle: From Requirement to Release

DEVELOPMENT Lifecycle From Requirement to Release,[object Object],UX Update Meeting,[object Object],20 April 2011,[object Object],Julie Meloni,[object Object],Lead Technologist/Architect,[object Object],Online Library Environment, UVa Library,[object Object],jcmeloni@virginia.edu // @jcmeloni,[object Object]

Functional requirements define the functionality of the system, in terms of inputs, behaviors, outputs.,[object Object],What is the system supposed to accomplish?,[object Object],Functional requirements come from stakeholders (users), not (necessarily) developers.,[object Object],stakeholder request -> feature -> use case -> business rule,[object Object],Developers can/should/will help stakeholders work through functional requirements.,[object Object],Functional requirements should be written in a non-technical way.,[object Object],Functional Requirements,[object Object]

Example functionality: representation and manipulation of hierarchy,[object Object],Description: The GUI should allow users to view and interact with hierarchical structures representing the intellectual arrangement and the original arrangement of files and directories within ingested accessions. For each component level in the intellectual arrangement, the user interface should present associated digital assets and an interface to view and edit descriptive metadata elements. ,[object Object],Specific Components: collapse and expand record nodes for viewing (applies to both the original ingest and the intellectual arrangement), add new child record, add new sibling record, copy all or part of the existing structure to the intellectual arrangement, delete a record in intellectual arrangement.,[object Object],Example Functional Requirement,[object Object]

An epic is a long story that can be broken into smaller stories.,[object Object],It is a narrative; it describes interactions between people and a system,[object Object],WHO the actors are,[object Object],WHAT the actors are trying to accomplish,[object Object],The OUTPUT at the end,[object Object],Narrative should:,[object Object],Be chronological ,[object Object],Be complete (the who, what, AND the why),[object Object],NOT reference specific software or other tools,[object Object],NOT describe a user interface,[object Object],Writing USE CASES (or epics),[object Object]

Stories are the pieces of an epic that begin to get to the heart of the matter.,[object Object],Still written in non-technical language, but move toward a technical structure.,[object Object],Given/When/Then scenarios,[object Object],GIVEN the system is in a known state WHEN an action is performed THEN these outcomes should exist,[object Object],EXAMPLE:,[object Object],GIVEN one thing ,[object Object],AND an other thing ,[object Object],AND yet an other thing ,[object Object],WHEN I open my eyes ,[object Object],THEN I see something ,[object Object],But I don't see something else,[object Object],Writing stories,[object Object]

Scenario: User attempting to add an object,[object Object],GIVEN I am logged in ,[object Object],AND I have selected the “add” form,[object Object],AND I am attempting to upload a file,[object Object],WHEN I invoke the file upload button,[object Object],THEN validate file type on client side ,[object Object],AND return alert message if not valid,[object Object],AND continue if is valid,[object Object],THEN validate file type on server side,[object Object],AND return alert message if not valid,[object Object],AND finish process if is valid,[object Object],Actual example,[object Object]

Developers involved at the story level,[object Object],Writing stories,[object Object],Validating stories,[object Object],Throwing rocks at stories,[object Object],Getting at the real nitty-gritty of the task request,[object Object],Moving from story to actual code,[object Object],Stories written in step definitions become Ruby code,[object Object],Tests are part of this code,[object Object],Code is tested from the time it is written,[object Object],Writing code,[object Object]

So, the butterfly effect…,[object Object],When one change in a complex system has large effects elsewhere, through a sensitive dependence on initial conditions.,[object Object],Epics and stories do not have to be golden, but changes should be carefully considered,[object Object],Developers illuminate the potential effects of changes,[object Object],The cycle of epic, story, coding begins again,[object Object],This includes any story that touches the changed story,[object Object],Never stop communicating,[object Object]

We don’t ever think we’re finished when we release a product,[object Object],Each release has with a list of known issues and potential areas of improvement,[object Object],We go through the cycle of epic, story, coding/testing, user testing, story editing, coding/testing, (etc) again and again.,[object Object],Products are organic and grow upward and outward,[object Object],…but if you want to lop off part of that tree, expect there will be systematic changes ,[object Object],Developers are there to ensure the tree doesn’t fall on your house.,[object Object],releasing,[object Object]

Development Lifecycle: From Requirement to Release

Development Lifecycle: From Requirement to Release

Recommended

More Related Content

Similar to Development Lifecycle: From Requirement to Release

Similar to Development Lifecycle: From Requirement to Release(20)

More from Julie Meloni

More from Julie Meloni(12)

Recently uploaded

Recently uploaded(20)

Development Lifecycle: From Requirement to Release