ih201585030 w2 mid enb submission

Course: SEF-2015 Engineering NotebookEngineer: Period: 07-12-2015 to 12-12-2015

Notes: (Record key insights from readings and discussions.)Introduction to story boards:Power Of stories: stories are effective tools which answer many questions like why,what,who,when,where,how(3:05)Stories are used to explain ‘A’ concept in A perspective and we need multiple stories to see in various perspectives which can be true at the same point at the same time(5:55)Storyboards: are a key design tool used by many where a series of images are drawn to highlight key elements and flow of the story. The notion of flow is key to story boardStory Board elements: Backstory,products,actions,pictures,flow

Story Boards-The FlowStory Boards are a combination of images and supportive text to help move the story forward where image is view of an application screen and text should provide what user should do next(1:58)If there is no flow, then it is not a story board(2:50)I

Story Boards-The BackStoryBackstory is a context that is needed to understand story board(0:45)It describes the specific problem so that the reader is able to understand what and how it should be done.(1:20)Creating a story board is iterative Start with the solution to a common problem(highlighting how should it work) Solution flow List the data needed(Back story data) Refine the flow with screen shots. Refine the list of data

Confidential Page: 1 of 6


Notes: (Record key insights from readings and discussions.) Iterate until the flow is obviousThe backstory provides the information to: Understand the problem Appreciate the flow Know what information should be provided

Know what buttons to pushTASK – PAIR OF USER STORIES: (05:18)

Enhancements to be done to DELLA 10:

Should add login feature to this application to provide security

for the work done by the teams.

Della 10 should work both in online and offline mode.

Multi user can access the application.

When multi users accessing the application, privileges to

modify/update the data should be given to one user and others

should have updates about the work done.

When in offline mode, the user can have read only access to

data.

When in online mode, the user can have both read and write

access to the data.

STORYBOARDS – THE BACKSTORY : (03:56)

A back story is not a story board.

A back story is not long and complex.

Back story is the setup that is needed for one to understand the



Notes: (Record key insights from readings and discussions.)

storyboards.

A back story describes a specific problem with just enough

detail so the reader is able to deduce what should be done, how

it should be done, and what information is needed.

What goes into back story : (01:38)

- Start with the solution to a common problem, highlighting

something that is key in how the application should work.

- Map out in very general terms the solution flow.

- List the data needed to support the flow.

- Refine the list of data and initial values from the flow.

- Refine the flow with screen shots with realistic data.

Telling Back story: (03:01)

Back story provides the information to :

- Understand a problem to solve.

- Appreciate the flow to solve the problem.

- Knows what the buttons push.

Knows what information should be provided to textboxes or selection lists.Presentation on Della Project:

PPT:o To tell the scenarios explained video why, how, and

when this Della project can be used.



Notes: (Record key insights from readings and discussions.)

o Added a Real Life Scenario where this project can be used( e.g.: To handleMSIT Mentor Student Details)

o Prepared the presentation on Della project using the screens we have developed.

o To show the added functionalities in the existing project.

o Added the enhancements we are going to work Narration for PPT:

o Narration for the PPT is given to explain the presentation in detail

Deliverable StatusDeliverables What did you plan to

accomplishWhat did you actually accomplish

Size Effort

Story Board To learn story board

I learnt about what is story board and how is it useful

12:21 30min

Story Board flow

To learn how to write story board

Learnt how to write story board

11:09+3.56

35 min



Notes: (Record key insights from readings and discussions.)And BackstoryStory Board PPT

To prepared a presentation on story board

Prepared a presentation describing problem statement and solution

1:30 hrs

ppt To create ppt explaining given scenario and real – life scenarios

Made A ppt on given scenario and my own scenario and also added enhancements to della

5.00hrs

Add Narration

To Add Narration To Each Slide

Added Narration to Each And Every Slide

2.30hrs

Lessons Learned ReflectionContext (e.g. The gap between plan and actual) Lesson

ENBPeer Review ON What Parameters We Need To Review Other ENB

Plan for the Next Week: (These items should appear in the deliverable status for the next week.)

Deliverable What do you intend to accomplish and why

Make a list of the critical requirements

A clear idea about what we require and how do we accomplish it.

Identify scenarios, to-be-added requirements, and useful elements from

Able to understand UML diagrams and apply it to Della



Plan for the Next Week: (These items should appear in the deliverable status for the next week.)

Deliverable What do you intend to accomplish and why

the original Della.Produce a draft fully-dressed Use Case models for the new Della.


Create Swim lanes and Sequence Diagrams for the key scenarios.


Use of GRASP patterns

Learn about GRASP patterns.


ih201585030 w2 mid enb submission

Documents