Professional Documents
Culture Documents
As a Software by doing
developer, i want to refactoring,code
refactor the code of will be more clear to
bank-operations understand and
project, so that code readable
Friday,20 October,2017 will more clear and
readable
As a software by doing this i get
developer, i want to overall view of my
draw software i can
container,component analyse the follow
and module diagram of software
of bank-operations
software, so that i get
overall view of
software
Acceptance Criteria1: we Task 1: write test cases first i will write test 4hours
have to pass information for every feature in cases based on features
through shell. application in application.
Acceptance Criteria2:we
have to pass in tuple
format like
{accountnumber,Accoun
tNUmber}
Acceptance
Criteria3:Passing
arguments in diiferent . Second i will test that 2hours
ways in function call like Task 2: test and find bugs cases and fixes the bug
passing lists,without using test cases.
arguments
when i have clear idea Task 1: write description i will explain about 10mins
about requirements of for project in readme file. my project and what it
my project. will do.
When i have listed out
user stroies.
When i write acceptance
criteria for every user
stroy.
When i rewrite the
readme file.
Task 2 : Analyse the i will analyse what are 20mins
reqiuements of project. the features of my
project the i will listout
all features.
when i understand Task 1: Spike : Study the first i will study and 9th
chapter
erlang programming chapters 9,10,11,12 from understand the 2hour
concepts of introducing erlang programming chapters 9,10,11,12 10th chapter
erlang document i.e; book then i will practice the 2hours
9)Exceptions, Errors, and concepts in shell and 11th chapter
Debugging programs given in 2hour
12th chapter
10)Storing Structured book. 1hours
Data
11)Getting Started with
OTP
when
12)Nexti understand
Steps Through Task 1: Spike : Study the first i will study and 5th chapter
erlang
Erlang.programming chapters 5,6,7,8 from understand the 1hour
concepts
-when i am of introducing
able to erlang programming chapters 5,6,7,8 then i 6th chapter
erlang book 2hours
deliverdocument i.e;
all this chapters will practice the
7th chapter
5)Communicating
from erlang document. with concepts in shell and
Humans programs given in 1hour
8th chapter
6)Lists book. 3hours
7)Higher-Order
Functions and List
Comprehensions
8)Playing with Processes.
when i understand Task 1: Spike : Study the first i will see how to 1st chapter -
erlang programming erlang programming install erlang in my pc 30mins
concepts and rules book then i will study 1st 2nd chapter-
chapter it will have 2hours
basic things how to use 3 chapter-
rd
We should know Task 1: understand how first i will find what 1hour(12p
following things: to implement the network layers are m-1pm)
1)what protocols we can protocol interface layer present in scc. Then i
add in that layer. in scc will find what are
2)how to add protocol dependency in scc.
interface layer in scc.
3)how protocol layer can
communicate with nemi.
4)know about FMC.
Task 2: learn how to first i search fmc plug- 1hour(1pm-
install the fmc plug-in in ins in eclipse website 2pm)
eclipse . then i will download
that plug-ins and i will
add to eclipse.
1)understand your Task 1: Search for the i will search in google Task1:
problem 2)Think some good documemt or and find information 1hour
possible solution for that information which about planning. (11am to
problem expain how to plan . What is planning. 12pm)
3)collecting required Task 2: Prepare the What steps involved in Task 2:
information presentation on planning. planning. 1hour(12p
4)make alternatives How to plan m to 1pm)
5)create timetable How to monitor our
6)review planning.
The task will be accepted Task 1: Understand the I am going to read the 2hours
when i write user story by structure for writing the document and (10 am to
answering the 3 questions user stories. understand the topics 12 pm )
(who, what, why) then Task 2:understand how one by one.
prioritizing the user stories user stories are
and implement in sprint. prioritized and divided
into sprints.
We should know following Task 1: Search for the first, i will google and 2hours (3
things: good book which expain find the book or point pm to 5 pm
1)following Top-Down how to write readable out some information )
model code from google how to make
2)giving meaningfull Task 2:understand the code readable.
variable name and function book and point out the
name features it have explained
3)Put commonly used code about code readable
into one module
4)Each function should
only have one "role"
5)Format programs in a
consistent manner
6)Dont write large modules
After Completing the task,
Review and Comment how
the task went? Did it go as
per the plan?
Interface diagram is
completed as per Plan.
Customer interface , chef
interface and waiter interface
diagrams are mailed.
Incomplete,finding in format
i have to write test cases