Task: 4

q  Discuss, as many as possible, other software management myths, customers myths
                              and practitioner myths.

                                            Software Myths
                 -  Erroneous beliefs about software and the process used to build it.

Management Myths
-  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 the Belief will lessen the pressure.

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 very well exist, but is it used?
- Are software practitioners aware of its existence?
- Does it reflect modern software engineering practice?
- Is it complete? Is it adaptable?
- Is it streamlined to improve time to delivery while still maintaining a focus on Quality?
In many cases, the answer to these entire question is no.
Myth     : If we get behind schedule, we can add more programmers and catch up (sometimes called the
                 Mongolian horde concept)
Reality : Software development is not a mechanistic process like manufacturing. In the words of Brooks :“Adding people to a late software project makes it later.” At first, this statement may seem counterintuitive. However, as new people are added, people who were working must spend time educating the newcomers, thereby reducing the amount of time spent on productive development effort

Myth     : If we decide to outsource the software project to a third party, I can just relax and let that firm build it.
Reality : If an organization does not understand how to manage and control software project internally, it will invariably struggle when it out sources software project.


Customer Myths
- A customer who requests computer software may be a person at the next desk, a technical group down
  the hall, the marketing /sales department, or an outside company that has requested software under
  contract.
- In many cases, the customer believes myths about software because software managers and
  practitioners do little to correct misinformation. Myths led to false expectations and ultimately,
  dissatisfaction with the developers.


Myth     : A general statement of objectives is sufficient to begin writing programs we can fill in details later.
Reality : Although a comprehensive and stable statement of requirements is not always possible, an ambiguous statement of objectives is a recipe for disaster. Unambiguous requirements are developed only through effective and continuous communication between customer and developer.

Myth    : Project requirements continually change, but change can be easily accommodated because software is flexible.
Reality : It’s true that software requirement change, but the impact of change varies with the time at which it is introduced. When requirement changes are requested early, cost impact is relatively small. However, as time passes, cost impact grows rapidly – resources have been committed, a design framework has been established, and change can cause upheaval that requires additional resources and major design modification.



Practitioner’s myths
- Myths that are still believed by software practitioners have been fostered by over 50 years of
  Programming culture.
- During the early days, programming was viewed as an art form. Old ways and attitudes die hard


Myth    : Once we write the program and get it to work, our job is done.
Reality: 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    : Until I get the program "running" I have no way of assessing its quality.
Reality: 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 more effective than testing for finding certain classes of software defects.

Myth   : The only deliverable work product for a successful project is the working program.
Reality: A working program is only one part of a software configuration that includes many elements. Documentation provides a foundation for successful engineering and, more important, guidance for software support.

resource : software engineering ( a practitoner approach) 5th edition book

Task: 4

Discuss, as many as possible, other software management myths, customers myths

                              and practitioner myths.

                                            Software Myths
                 -  Erroneous beliefs about software and the process used to build it.

Management Myths
-  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 the Belief will lessen the pressure.

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 very well exist, but is it used?
- Are software practitioners aware of its existence?
- Does it reflect modern software engineering practice?
- Is it complete? Is it adaptable?
- Is it streamlined to improve time to delivery while still maintaining a focus on Quality?
In many cases, the answer to these entire question is no.
Myth     : If we get behind schedule, we can add more programmers and catch up (sometimes called the
                 Mongolian horde concept)
Reality : Software development is not a mechanistic process like manufacturing. In the words of Brooks :“Adding people to a late software project makes it later.” At first, this statement may seem counterintuitive. However, as new people are added, people who were working must spend time educating the newcomers, thereby reducing the amount of time spent on productive development effort

Myth     : If we decide to outsource the software project to a third party, I can just relax and let that firm build it.
Reality : If an organization does not understand how to manage and control software project internally, it will invariably struggle when it out sources software project.


Customer Myths
- A customer who requests computer software may be a person at the next desk, a technical group down
  the hall, the marketing /sales department, or an outside company that has requested software under
  contract.
- In many cases, the customer believes myths about software because software managers and
  practitioners do little to correct misinformation. Myths led to false expectations and ultimately,
  dissatisfaction with the developers.


Myth     : A general statement of objectives is sufficient to begin writing programs we can fill in details later.
Reality : Although a comprehensive and stable statement of requirements is not always possible, an ambiguous statement of objectives is a recipe for disaster. Unambiguous requirements are developed only through effective and continuous communication between customer and developer.

Myth    : Project requirements continually change, but change can be easily accommodated because software is flexible.
Reality : It’s true that software requirement change, but the impact of change varies with the time at which it is introduced. When requirement changes are requested early, cost impact is relatively small. However, as time passes, cost impact grows rapidly – resources have been committed, a design framework has been established, and change can cause upheaval that requires additional resources and major design modification.



Practitioner’s myths
- Myths that are still believed by software practitioners have been fostered by over 50 years of
  Programming culture.
- During the early days, programming was viewed as an art form. Old ways and attitudes die hard


Myth    : Once we write the program and get it to work, our job is done.
Reality: 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    : Until I get the program "running" I have no way of assessing its quality.
Reality: 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 more effective than testing for finding certain classes of software defects.

Myth   : The only deliverable work product for a successful project is the working program.
Reality: A working program is only one part of a software configuration that includes many elements. Documentation provides a foundation for successful engineering and, more important, guidance for software support.

resource : software engineering ( a practitoner approach) 5th edition book

Tun Mahathir Lecture Series




Last 13th December 2010, Tun Mahathir Lecture Series was held in Uniten. The lecture is base on the topic “Globalizing Malaysian in 2020”.  This is the list about the program tentative.



9.00 a.m : Arrival of Guests
9.40 a.m : Arrival of Y.Bhg Tan Sri Leo Moggie
Chairman Board of Director, UNITEN
 9.45 a.m : Arrival of Y.A.Bhg Tun Dr. Mahathir bin Mohamad
10.00 a.m : National Anthem
: UNITEN Song
: Doa Recital
10.15 a.m : Welcoming Address by Y.Bhg Tan Sri Leo Moggie
 10.30 a.m : UNITEN Tun Mahathir Lecture Series by
Y.A.Bhg Tun Dr. Mahathir bin Mohamad
"Globalizing Malaysians in 2020"
11.30 a.m : Q&A
 12.00 a.m : End




The speaker for this series of lecture is Tun Mahathir himself. Tun talked about the globalization that happened all around the world. Our country is a part of the globalization but it is base on western globalization. The globalization has their pros and cons for each country that been involved. Tun said in this lecture that we should make our own globalization instead of using western because it may lead to less contribution to raise the country. For example, some students went to overseas to continue their studies but after they finished their studies, they prefer stay overseas to start their career because of the income is better than start the career in Malaysia.

The duration of this talk by Tun Mahathir is about an hour and the candidates who were attended to this lecture gave their question to Tun base the current issue and the current topic of the talk. The time given for question and answer session doesn’t enough for all candidate who want to ask the question to Tun Mahathir. After that Q & A session ends, Tun Mahathir leave the hall and the lecture series of Tun Mahathir ends.

  

Task: 3

Task: 3

qAnalyze the entire job titles posted in the http//www.jobstreets.com.my, which are related to the software engineering professionals advertised on 9 -11 Dec 2010. Create a table of several rows and columns. The rows should represent the job title (and/or its synonyms) and the columns should represent the following:
1.  The dates (3 columns), company names (or names of advertisers), descriptions of the job, requirements of the job and the salary range of the job title. In each date column, state the frequency of the advertised job title.  
2.Write a summary of the created table.
3.State what you can conclude from the findings.
qUpload the table, summary of the table and conclusion from your findings in you blog by the given deadline.




   
Conclusion

                  Based from our findings on job analysis above, we can conclude that most of the professionals need skills that required for higher job title and also have long experience in working in their area of expertise. Most of them also possess higher education to fill in the job title related to the software engineering courses.

Task: 3

Task: 3

qAnalyze the entire job titles posted in the http//www.jobstreets.com.my, which are related to the software engineering professionals advertised on 9 -11 Dec 2010. Create a table of several rows and columns. The rows should represent the job title (and/or its synonyms) and the columns should represent the following:
1.  The dates (3 columns), company names (or names of advertisers), descriptions of the job, requirements of the job and the salary range of the job title. In each date column, state the frequency of the advertised job title.  
2.Write a summary of the created table.
3.State what you can conclude from the findings.
qUpload the table, summary of the table and conclusion from your findings in you blog by the given deadline.




   
Conclusion

                  Based from our findings on job analysis above, we can conclude that most of the professionals need skills that required for higher job title and also have long experience in working in their area of expertise. Most of them also possess higher education to fill in the job title related to the software engineering courses.

Task: 2

Task: 2
qComplete the software application domain matrix (refer Mod1.ppt)
qProvide 5 examples software for each domain.
qUpload the matrix in your blog by the given deadline.

Domain

Characteristic

Example Software

System
software
·         a collection of programs written to service other programs.
·         Some system software processes complex, but determinate, information structures.
·         It is characterized by heavy interaction with computer hardware
·         It is heavy usage by multiple users
·         concurrent operation that requires scheduling, resource sharing, and sophisticated process management
·          complex data structures
·         multiple external interfaces

·         editors
·         file management utilities
·         OS – MS Windows, Linux Ubuntu
·         Drivers – printer driver
·         Networking software - wireless networking software
·         Telecommunication software – messaging system such as sms, mms
·         Compilers – Borland C++, Turbo C
·         BIOS Software
·         HD Sector Boot Software
Application
software
·         Application software consists of standalone programs that solve a specific business need
·         run under System Software
·         Format of information displayed
·         High-speed user interaction
·         facilitates business operations or management/technical decision-making.
·         used to control business
functions in real-time
·         point-of-sale transaction processing
·          real-time manufacturing process control
·         word processing software-Microsoft Word
·          spreadsheet software-Microsoft Excel
·         database software-MySQL
·         presentation graphics  software-Microsoft Powerpoint, iTunes, World of Warcraft, Adobe Photoshop
·         Web browser –Opera






Engineering/
scientific
software
·         Formerly characterized by "number crunching" algorithms, engineering and scientific software applications range .
·         Complex formula evaluation
·         Very high accuracy
·         Interaction with data collection devices
(e.g. Sensors) often at high speeds
·         High resolution graphic displays of large amounts of data
·         Parallel and multi-processor applications
·         Computer-aided design
·         system simulation
·         Flight simulator
·         computer-aided engineering (CAE)
·         ECAD software-
KiCad ,Eagle
·         Circuit Analysis and Schematics-PSpice , Multisim Designsuite 9
Embedded
 software
·         resides within a product or system and is used to implement and control features and functions for the end user and for the system itself.
·         perform limited and esoteric functions
·         provide significant function and control capability
·         Human Machine Interface software,
·         Graphics software
·          Enterprise resource planning software,
·         communication software
·         mobile and wireless software

Product-line
 software
·         Designed to provide a specific capability for use by many different customers
·         product-line software can focus on a limited and esoteric marketplace or address mass consumer markets.
·         can also enable rapid market entry and flexible response, and provide a capability for mass customization
·         usually aimed at a well-defined market segment.


·         Ms Word
·         word processing, spreadsheets
·         computer graphics
·         multimedia
·         entertainment
·         database management
·         personal and business
·         financial applications
Web-
applications
·         span a wide array of applications
·         little more than a set of linked hypertext files that present information using text and limited graphics
·         provide standalone features, computing functions, and content to the end user
·         integrated with corporate databases and business applications
·         integrate easily into other server-side web procedures
·         provide cross-platform compatibility in most cases


·         webmail- Gmail or Yahoo mail
·          online retail sales
·         online auctions
·          wikis
·         Google Apps
·         Microsoft Office Live
·         WebEx WebOffice
Artificial
 intelligence
software
·         AI software makes use of nonnumerical algorithms
to solve complex problems that are not amenable to computation or straightforward analysis .

·         Robotics
·         expert systems
·         pattern recognition (image and voice)
·          artificial neural networks
·          theorem proving
·          game playing


resource : software engineering ( a practitoner approach) 5th edition book