Assignment 1 / task 2 : software application domain matrix.

Domain	Characteristic	Example Software
System Software	•       Generally, programs written to service other programs. •       Heavy interaction with computer hardware. •       Heavy usage by multiple users. •       Concurrent operation that requires scheduling. •       Resource sharing and sophisticated process management. •       Complex data structures. •       Multiple external interfaces.	•       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.
Application Software	•      Used to control business functins in real life time •       Also called end-user programs. •      Control business functions in real-time •       Applications in this area process business.	•       Point-of-sale (POS). •       Media players. •       Spreadsheets- Microsoft Excel. •       Word processors- Microsoft Word. •       Web Browsers- Mozilla Firefox.
Engineering/ Scientific Software	•      From automotive stress analysis to space orbital dynamics •       Number of crunching algorithm Ranges from astronomy to volcanology	•       Flight simulator •       computer-aided design (CAD). •       CAT scans. •       DNA analyses. •       Computer-aided Engineering (CAE).
Embedded Software	•      Used to implement and control features and functions for the end user and for the system itself. Embedded software can peform limited and esoteric functions or provide significant function and control capibility •       Its main role is to interact with the physical world. •       Designed to do some specific task, rather than be a general-purpose computer for multiple tasks. •     Performs limited and esoteric functions	•       Software to control robots’ movement. •       Consumer electronics-personal digital assistants (PDAs). •       Medical equipment   for vital signs monitoring- electronic stethoscopes. •       large stationary installations. •       controlling nuclear power plants.
Production-line Software	•       Address mass customer markets •      Focus on a limited and esoteric market place Provide a specific capability for use by many different customers •       Utilize multiple binding times.	•       Microsoft Word. •       Microsoft Excel. •       Microsoft Powerpoint. •       Microsoft Outlook. •       Automobile Development.
WebApps	•       They are evolving into sophisticated computing environments that not only provide standalone features •       It has the convenience of using a web browser as a client. •       Intergrated with corporate database and business application Set of linked hypertext files that present information using text and limited graphics •       Integrate easily into other server-side web procedures.	•       UNITEN Online Application System. •       Blogspot. •       Facebook. •       Myspace. •       Hotmail.
AI Software	•            Knowledge-based systems render their evaluation somewhat their different than conventional algorithmic software •            Problems that are not amenable to computation or straightforward analysis •             Learning system Computer changes how it functions or reacts to situations based on feedback. •             Neural network Computer system which simulate the human brain function.	•       Expert system – Diagnostic Medical   expert system •      Computer perception •      Voice recognition system •      Speech synthesizer •      Blackboard system

Assignment 1 / task 3 - jobs from the Jobstreets

In task 3, we are assign to list down all jobs that are related to software engineering professionals on 9 till 11 December 2010

Job Analysis

Job title	Dec 9, 2010	Dec 10, 2010	Dec 11, 2010	Advertisers	Job descriptions	Job  requirements	Salary Range (in RM)
software programmer	2	1	3	* Silvercom Technologies. *Tiseno Integrated Solution Sdn,Bhd	* Participate in the complete software development life cycle *Provide Technical support.	*Bachelor's Degree, Post Graduate Diploma, Computer Science/Information Technology. *C++ or PL/SQL.NET *6 months of working experience.	2000-3500
software Engineering	2	-	-	Apple (malaysia) Sdn.Bhd	*Design and construct system based on user requirement	*At least passed Bachelor's Degree in computer science/Information Technology. *one years of working experience  (at least) *Good Knowledge of Java programing language. include JSP, JDBC.	3000-4500

Assignment 1 / task 4 - Myths

The word “myth” based from Wikipedia is a word that is often used colloquially to refer to a false story, however in terms of academic, the word generally means does not pass judgment on truth or falsity. Therefore in my opinion, the word “myth” simply means something that is assumed exists but there is no proof about its existence.


Software myths can be classified to 3 (THREE) which are:
1. Management myths
2. Customer myths
3. Practitioner myths


Some common managerial myths stated by Rogher Pressman are:
Myth: A good manager can manage any project.

Reality: In a high stake project especially a software project that costs a lot of money, an expert is needed to manage it carefully. To ensure a good project management, developer’s company will need a manager that can manage one thing that he can do adeptly, not a manager that can manage MANY things but he cannot do it adeptly.

Myth: If I 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.

The second myth that I will tackled is the customer myth:

Myth: I know what my problem is; therefore I know how to solve it.

Reality: Customer may know how to solve it. However from developer’s point of view, the way customer wants to solve it may not be as same as the way the developer wants to solve it. Therefore by maintaining good communication between both parties can guarantee that the needs can be met.

The third myth which is the last is practitioner myth :

Myth: If I miss something now, I can fix it later.

Reality: Whenever something is missed, especially in earlier development stage, we should immediately get it done because if one thing is missed and we only notice it in later stage, a very major modification needs to be done and it will consume much time and will become a big problem to the team.

References:

* Wikipedia.