Please enable JavaScript.
Coggle requires JavaScript to display documents.
(SDPM, what role can i use if developing a library to be used by future…
-
-
application programmers, but not programmer, which is too vague as it could denote the dev team
-
-
-
-
performance requirements, scalability, portability
-
-
-
name the classes of users, the interfaces and the relationships between them
application developers, calculation consumers, and calculation authors
the API, the command-line interface (CLI), and the graphic user interface (GUI)
app devs use the API, consumers and authors use the CLI and GUI
if different users want the same functionality, but through different interfaces, should they be merged or remain split?
keep them split since they can only be implemented separately, and because the GUI is lower priority
-
-
-
what are the dependencies, if any, between these stories?
there might appear to be a dependency of the latter two upon the first, but that functionality can be demonstrated using a stub before getting it implemented.
an implicit dependency that can be ignored is that a spreadsheet would have to be created before being loaded or modified
-
-
possibly, it is a broad statement that could be broken down into:
-
-
As an application developer I would like to add an expression with operators to a cell in a spreadsheet.
As an application developer I would like to add an expression with function calls to a cell in a spreadsheet.
-
-
-
can be complicated by the use of areas, so we might want to split these:
-
As an application developer I would like to load a spreadsheet from a file containing only simple assignments.
As an application developer I would like to load a spreadsheet from a file containing area references.
-
As an application developer I would like to save a spreadsheet with one assignment per non-empty cell.
As an application developer I would like to save a spreadsheet using AreaReferences to compress the output.
-
lots of code, but you know what to do
know what to do, but will take time
know what to do, but challenging
-
What’s the smallest set of stories that we could seek to implement in one increment period that leaves us a “working” demonstration?
based on estimates, select stories that add up to 5 units of effort for one increment
-
-
Bug Stories - fixes for bugs that passed unit testing, hard to estimate so allocate fixed time then schedule a follow up
Spike Stories - lack of info to estimate a story, "Research how to estimate story X"
-
a runnable program that demonstrates a new functionality, a functionality of a single story might not always be visible
-
in scrum agile process model, a period of development for one increment
-
-
task board - includes in progress(to do/ sprint backlog) and completed stories,
-
-
-
when a story is picked for implementation, what is done with it?
list the required tasks, track their completion status, where tasks belonging to multiple stories can be alternated between, with tests for each section of implementation being written incrementally
-
-
-
-
-
-
-
-
return to 18 after future lessons regaurding repository, build file, unit test, commit
-
write a test that will initially fail (if it can be run at all) before implementation to know when we have succeeded with implementing it and so that we have a test driver ready once we have written the code
-
checklist that must be completed before a story/task is considered completed and work reassigned; defined at the start of the project, typically a story is split into tasks using the definition of done criteria
-
code passes all unit tests, System level (functional) tests
-
-
-
reviewed by other team members and analysis tools, and found free of major problems.
user stories are an incremental and iterative design model, what does the iterative part mean?
-
-
-
-
hard - ADTs, especially complicated ones
-
-
-
user stories
-
-
simple description of a desired functionality(something the customer wants), often 1-2 sentences, index cards, clear completion criteria(validatable[can be shown to the customer])
small sets of stories are selected for each new increment for construction, as many as the time window will allow us to complete before moving on to the next increment, and enough to be visible.
-
customer-centric - uses customer's POV, can be written by the customer or ranked by priority by the customer/dev team. as a [insert customers's role here{NEVER use 'user' or your own role as the role], i would like [desire] so that [benefit]
estimatable - how much time to complete a functionality, using relative with average time to complete a story == 1.0; 1.5 = harder than last time by half as much
validatable - measured in percentage, definition of done = criteria decided by team, such as passing unit tests, being documented, being integrated