A2 Task 1

INCREMENTAL MODEL

CHARACTERISTIC :

• Hybrid model that combines elements of the waterfall and evolutionary paradigms
• The specification, design, andimplementation phases are broken in smaller increments
• The system is created so that it can be delivered in pieces, enabling the users to have some functionality while the rest is being developed.

STRENGTH :

• Provides better support for process iteration
• Reduces rework in the software construction process
• Allows early delivery of parts of the system

WEAKNESS :

• Increments need be relatively small
• Mapping requirements to increments may not be easy
• Common software facilities may be difficult to identify

APPLICABLE :

• When it is possible to deliver the system part- by-part
• Software/System Projects are involve with new technology.
• There is a need to know the early realization of benefit from the system.

PROTOTYPING MODEL

CHARACTERISTIC :

• Prototyping is a technique for providing a reduced functionality or a limited performance version.

STRENGTH :

• Encourages active participation among users and producer.
• May provide the proof of concept necessary to attract funding.
• Enables a higher output for user.

WEAKNESS :

• Producer might produce a system inadequate for overall organization needs.
• User can get too involved whereas the program can not be to a high standard
• Structure of system can be damaged since many changes could be made

APPLICABLE :

• Prototype are good in demonstration.
• Incomplete versions of the software program being developed

SPIRAL MODEL

CHARACTERISTIC :

• Four sectors per loop: objective setting, risk assessment and reduction, development and validation, planning
• Risk is explicitly taken into consideration
• Also a hybrid model that support process iteration

STRENGTH :

• Risk reduction mechanisms are in place
• Supports iteration and reflects real-world practices
• Systematic approach

WEAKNESS :

• Requires expertise in risk evaluation and reduction
• Complex, relatively difficult to follow strictly
• Applicable only to large systems

APPLICABLE :

• Internal development of large systems
• The goals are unstable but the architecture must be realized well enough
• Requirement are complex and complicated

EXTREME PROGRAMMING

CHARACTERISTIC :

• intended to improve productivity and introduce checkpoints where new customer requirements can be adopted.
• needed, a flat management structure
• simplicity and clarity in code
• more free-form and unplanned

STRENGTH :

• Not necessarily have to define a stable set of requirements.
• Cost effectiveness on formal overhead.
• Help developers to produce high quality software.

WEAKNESS :

• Difficulty coordinating larger teams
• Can result in a never-ending project if not managed properly
• Tendency to not document thoroughly

APPLICABLE :

• when the system functionality is exected to change every few months.
• if customer do not set the dateline for the system to be done, if else, the risk will be more greater.
• XP is suitable within small number of programmer, and the dont need the programmer with Ph.D to use XP.

REFFERENCE :

http://www.softdevteam.com/Spiral-lifecycle.asp

http://en.wikipedia.org/wiki/Spiral_model

A1 Task 4

SOFTWARE MYTH

Myth is an erroneous beliefs about software and the process that is used to build it which can be trace to the earliest days of computing. In software engineering, there are three types of myth that have to be highlight. These are includes management myth, customer myth and practitioner’s myth.

MANAGEMENT MYTH

Managers with software responsibility, like managers in most disciplines, are often under pressure to maintain budgets, keep schedules from slipping, and improve quality. Like a drowning person who grasps at a straw, a software manager often grasps at belief in a software myth. if that belief will lessen the pressure (even temporarily).

MYTH 1 :
If I decide to outscore the software project to a third party, I can just relax and let that firm built it

REALITY 1 :
If an organization does not understand how to manage and control software projects internally, it will invariably struggle when it outsourses software projects.

MYTH 2 :
If I decide to outscore the software project to a third party, I can just relax and let that firm built it

REALITY 2 :
If an organization does not understand how to manage and control software projects internally, it will invariably struggle when it outsourses software projects.


CUSTOMER MYTH
Myths that lead to false expectations by the customer and result in dissatisfaction with the developer. Problem with :

MYTH 1 :
Poor up-front definition is the mayor cause of failed SW efforts. Detailed description of function, performance, interfaces, design constraints and validation criteria essential.

REALITY 1 :
A formal and detailed description scan be communication determined only after thorough between customer and developer.

MYTH 2 :
Project requirements continually change„ but change can be easily accommodated because software is flexible


REALITY 2 :
It is true that software requirements changes, but the impact of changes varies with the time at which it is introduced.


PRACTITIONER MYTH
Myth that are still believed by software practitioners have been fostered by over 50 years of programming culture. During the early days of software, programming was viewed as an art form. Old ways and attitudes die hard.

MYTH 1 :
Job is done once we write and get the program work.

REALITY 1 :
Someone once said that the sooner you begin writing code, the longer it’ll take you to get done. Industry data indicate that between 60 and 80 percent of all effort expended on software will be expended after it is delivered to the customer for the first time.

MYTH 2 :
I should not accessing the quality, until i got the program running.

REALITY 2 :
One of the most effective software quality assurance mechanisms can be applied from the inception of a project – the formal technical review. Software reviews are a “quality filter” that have been found to be more effective than testing for finding certain classes of software errors.



References :

http://pswlab.kaist.ac.kr/courses/cs550-07/ch1.pdf
http://www.slidefinder.net/c/cpsc_333_seng_311_foundations/5493755
http://google.com
http://www.wikipedia.org

A1 Task 3

SUMMARY

In the table we have 3 job titles from random company accross Malaysia including advertiser,salaries and requirement.The table shown the occurence of the advertist jobs during 9th - 11th December 2010 at the JobStreet website.Most of the company required candidates possess at least a Bachelor's Degree or Post Graduate,Professional Degree required skill in C programming,SQL,CSS and more preferable applying with at least 2 year(s) of working in related field.

CONCLUSION

From the table above, they are many job opportunities in IT field. We can say that the software engineering is the most sought-after job title out there by people who are seeking for IT-related job in Malaysia. In addition, the needed for the job is highly demand. Therefore, there will be a competitive in the need of skill and commitment in job. Additionally, the least job advertise is senior software engineering.


To view our table, click here

Assignment 3 : Task 3PART 2

Assignment 3 : Task 3

PART 2

Assignment 3 : Task 3

PART 1

Assignment 3 : Task 2

Assignment 3 : Task 1