knowledge module

knowledge module

1. SLDC

   • feasibility study
     • find the scope of the problem and determine solutions
     • project plans, schedules, business case document
     • what's the return on investments?
     • people involved
       • product owners
       • execs
       • product managers
       • business analysts
   • requirements analysis
     • consider functional requirements of the project
     • analyse needs of end users to ensure needs are met
     • document listing requirements
       • functional
       • non functional
     • what should the system do?
     • people
       • domain experts
       • users
       • business analysts
   • design
     • specifications, d#features and operations that will satisfy functional requirements of the system
     • models and diagrams
     • what design meets the requirements?
     • how should the system do it?
     • technical architects
   • code development
     • development begins
     • produce testable and functional software
     • what code do we write to meet the design specification?
     • what technical components meet the design?
     • software developers
   • testing
     • system integration and testing
     • determine if goals have been met
     • test plans and test scripts
       • unit tests
       • integration tests
     • does it meet the requirements?
     • does everything work?
     • software testers
   • deployment / implimentation
     • majority of code has been written
     • project is put into production
     • implementation and deployment plans
     • operational system in the live environment
     • how do we go live?
     • release managers
   • maintenance
     • system is fine tuned
     • meet any additional needs
     • produce a maintenance report
     • how do we keep the system running?
     • people
       • database admin
       • system admin
       • third-line support

2. methodologies

   • agile
     • iterative approach, allows changing scope of the project
       • best when the scope if unknown
     • starts with a simple design which is divided up
     • customer communication is important
     • allows for partial success
     • products tested during the development cycle
     • rapid value
     • flexibility to oversee the development project
     • evolutionary SLDC
   • waterfall
     • sequential approach, changes cant be made
     • scope is known beforehand
     • communication only needed at set milestones
     • no partial success
     • testing can only be done at the end
     • little flexibility, products based on documented requirements
     • easier to control cost and scope
     • linear SLDC

3. other methodologies

   • scrum
     • used in agile project management
     • daily communication
     • flexible reassessment of plans
     • short iterative phases
   • spiral
     • risk-driven
     • adopts elements from one or more process
   • v model
     • enhanced version of waterfal
     • each level is verified before moving on
     • testing starts at the very begginging
   • RAD
     • emphasises on prototyping and iterative delivery
     • alternative to waterfall
   • lean
     • eliminate waste
     • amplify learning
     • decide as late as possible
   • XP
     • higher quality code more productively
     • reduce the cost of changes in requirements
     • lots of short development cycles

4. people in the team

   • business roles
     • sponsor
     • business analyst
     • domain expert
     • end users
   • project roles
     • project manager
     • team leader
   • technical roles
     • technical architect
     • solution developer
     • solution tester
   • implementation and support
     • release manager
     • database administrator
     • system administrator