Assignment 3 : Task 5

Assignment 3 : Task 4

Assignment 2 (Task 2)

Analyzation
From what i have been analyze, the SDLC used by KBase is a bit difference from what have i learn in class.

Combination of Off-shore + On-site + Hybrid Delivery Model

Model : Off-shore Delivery Model

Strengths :
1. On Time Within Budget Deliveries
2. Shortened Lead Times for Project Start-Up
3. Significant Cost Advantage
4. Strong Project Management Expertise
5. Highest Quality Standards
6. Access To Diversified Pool of Skilled Professionals
7. Shortened Development Cycles

Weakness
1. Missunderstanding with the clients
2. lacks of skills
3. Low maturity




Model : Onsite Delivery Model


Strengths
1. Face-to-face dealings with the clients
2. No chance of communication gap
3. On Hand Information
4. Reduce time to market



Model : Hybrid Delivery Model


Strengths
1. Direct dealings with the client:
2. 24/7 productivity:
3. Access to the most excellent resources:
4. Great cost benefits:

Assignment 3: Task 7

Module 7: Software Quality Management

Please click for large and clearer view.

Thank you. :)

Assignment 3: Task 6

Module 6 : Software Verification and Validation

Please click for a large and clearer view.

Thank you. :)

Assignment 2: Task 1 : Incremental Model Analysis

Characteristics	Strength	Weakness	Applicability
It is functioning in parallel; production and development.	Customer can give response to each increment.	The total cost of the complete system is high.	When projects have lengthy development schedules.
It enables the users to have some functionality while the rest is being developed, in which it can be delivered in pieces.	The development team can focus on different area of expertise with different releases.	A well-defined and detailed module interfaces are required.	When projects involve in new technology.
Development system is the next version that is being prepared to replace the current production system.	Markets can be created early for special functionality that has never been offered.	Requires early definition of a complete and fully functional system to allow for the definition of increments.	There is a need to know the early realization of benefit from the system.

Task 4 : The Softwear Myths

Software Myths

1.Erroneous beliefs about software and the process that is used to build it.

2.Misleading attitudes that have caused serious problems for managers and pactitioners.

Classifications of software myths

• Management Myths
• Customer Myths
• Practitioner Myths

Management Myth

Myth - We already have a book that's full of standards and procedures for building software. Won't that provide my people with everything they need to know.

Reality - The book of standards may exist, but is it used?Are Practitioners' aware of its exestence?Does it reflect modern SE practices?Is it complete?Is it adaptable?

Customer Myth

Myth - Software requirement continually change, but change can be easily accommodated because software is flexible.

Reality - The impact of change varies with the time at which it is introduced. The cost of impact of changes in early stage of software project is relative small.However, changes introduced at a later development stage may requires a lot of resources and major design modification.

Pratitioner Myth

Myth - "Once we write the program and get it work, our job is done."

Reality - Some once said the "the sooner you begin 'writing code', the longer it'll take youto get done".