Task: Build a Simplest Accounting S/W• You’ve been offered to build a very basicaccounting software for Bangoo Banks Inc.– You’ll need to collaborate with 3-4 otherdevelopers.– You’ll receive handsome amount of cash for fullfunctional software!– Deadline: very, very strict. Say, couple of months?
What are you going to do?• Divide the total project in visible sections, say:– User Accounts– Human Resource– Accounting– Etc…• And started asking questions to your clientshow they want the program behave, designdatabase…
All four developers started coding asfast as you can to maintain deadline.
After some days… you felt likeintegrating your works?• But you figured out you need a change in somepart, you could change it, but others’ code canbreak?• You hardly understand what your friend means byvariable baln or function register()• Your disc crashed and your codes are gone?• You’ve created too many folders like code_oldcode_working, code_new2, code_final… nowwhat?• How do you merge everybody’s code to a full-functional system?
Messed Up?• Without putting your code in a function, you just wroteit down, thinking, “Hey, I’ll not use this code anywhereelse! So Why do I need to put it in a function or class?”• But, you never know…– Client may change his mind– New functionalities may appear in future– And you’re very likely to duplicate same codes.– Man is mortal. To fix buggy codes you’ll need to investigateyour whole project number of times you copy-pasted samecode.• Hard to find bugs.
Software Evolves…• If your software is usable, it will have changesin it and have future releases.• Clients will add new features, or users willwant changes.
After some days, you’re about to bringsome changes in your code.
Introducing SADD• Systems…– Step 1: Analysis– Step 2: Design– Step 3: Development• Step 4: Evolve! Back to step 1
First Step: Systems Analysis• Known as Requirement Analysis• Extract information from your clients on whatthe software is supposed to do.• Place them on SRS Cards• Useful to understand the total scope ofapplication, defining priority and leads tomodular design.
Sample Requirement Analysisfor some Alumni Website…
SRS (Software Requirement Specification)Cards for Requirement Analysis
Step 2: Design your system• Once you’re done with analysis, design it.• The great majority of the types of errors foundin testing the code had originated in thedesign phase– See figure in next slide.
Systems Design• Following Design Patterns– Why reinvent the wheel?• Modular Design– Loosely coupled code– Easy to extend your program– Code less. Reuse your code• Build Wireframes• Follow Single Responsibility Principle
Building Wireframe• Create Mock-up/prototype of your applicationbefore starting coding.– Can be built using GUI tools very rapidly– Client can know how your application will looklike/interact with users.– Non functional.
Documentation• You alone are not coding– Others will work with your code– You will work with other’s code.• Provide Documentation
Take help of Development Tools• You figured out you need a change in somepart, you could change it, but others’ codecan break?• You hardly understand what your friendmeans by variable baln or functionregister()• Your disc crashed and your codes are gone?• You’ve created too many folders likecode_old code_working, code_new2,code_final… now what?• How do you merge everybody’s code to afull-functional system?
Understanding Your ResponsibilityYou need towork with alot of people!
Project Management Tools• Coding is not your only responsibility.– Issues are assigned to you by your ProjectManager– Bug fixing tasks assigned to you– You fix code and re-assign it to Tester.• To simplify all these, various Tools areavailable.– Using these tools guarantee standards.
Tools: Revision Controlling• Git is a powerful distributed versioncontrolling system.– Stores complete history of your source code atdifferent stages of project life cycle.– Easy merging of everyone’s copy of work.– Distributed.
Project Management Tools• Project Management applications come withrich features like– Role Management (PM, Tester, Designer,Programmer,…)– Bugs Reporting– Issue Tracking & Assigning– Gaunt Charts for schedule management– Documentation