Task 4 : Software myths

Software Myths – erroneous beliefs about software and the process that is used to build it    

There are three types of myths :

·         Management myth

·         Customer myth

·         Practitioner myth

Management Myths 

Myth 1 : 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 is :

Are we rolling, KIDDING ;)

The book of standards may exist, and we read, but is it we understand the meaning of point stated in the book? HAAAAA

When the designer design a software, are they follow exactly what the book said?
 

Customer Myths 

Myth 1 : Project requirements continually change, but change can be easily accommodated because software is flexible. 

Reality is :

The beginning of the project, we decided to follow what we going to do, step by step, but, eg : when the management changes, then the new step are been introduced so we have to say “bye” to the old steps and follow the new one.

Practitioner Myths

Myth 1: Job is done once we write and get the program work.
Reality is :
if we decided to do the project in last minute time, there is no 100% successful of the project will end up.

Muhammad Rijaluddin Bin Mohd Rusli (IS085739)

Muhammad Naqib Bin Md Esa (IS085723)

Task 3 : jobstreet.com

Summary - from 1 until 3rd June 2011, there are only Intership for Computer/ IT Sudents are offered by :

1. Xylog Computer System SDN BHD - Kuala Lumpur
2. AdExcel Online Network SDN BHD - Mid Valley City
3. Vision Technology Consulting SDN BHD - Petaling Jaya, Cyberjaya

This job needs a professional in :

• Oracle Applications, PL/SQL, Database OR Java Development
• Skills: .NET, Java, PL/SQL

• Build web applications using high tech tools and methods. Use open source tools such as Python, Django, Linux, PostgreSQL
• Skills: Java/PHP, SQL, CSS

Muhammad Rijaluddin Bin Mohd Rusli (IS085739)

Module 2

Software Processes

 Method(s) best used to study the module.

• Form a small group. Divide each sub topic to each members of group. Study about half an hour.
• Use a mind map.
• Ask each one of group members about their sub topic. Q&A.

Suggestion on topics that should be added or dropped from the module.

• The specialized process models sub topic should be dropped because in this chapter we had study the prescriptive process models. There is no need to focus on specialized process models. 

Suggestion on any other teaching and learning technique to be used during lecture.

• Students should read the notes in one hour time.
• Do some exercise and discussion with the lecturer.
• At the end of the class, give a pop quiz or Q&A session to the students.

All the lessons learned.

• There are four types of process flows - linear, iterative, evolutionary and parallel.
• Software process patterns may suggest one or more proven solutions to the problem from other projects, which can be reused in another project.
• There are four types of prescriptive models - waterfall, incremental, evolutionary(spiral & prototyping) and concurrent.
• There are several process assessment and improvements frameworks that can be exercised by practitioners.
• With the prescriptive and specialized process models, it would help to select the best process models for a software development project.

Mohammad Naqib Bin Md Esa (IS085723)

Module 1

Introduction to Software Engineering

Method(s) best used to study the module.

• Form a group, divide each main topic to every members of group, present the topic by group (Group)
• Create a table in notebook, list the Software Application Domain and state the characteristic and example for each of it (Individual)

Suggestion on topics that should be added or dropped from the module.

•  Don't have any suggestion, i guess. Because all the topics are related with each other.

Suggestion on any other teaching-and learning technique to be used during lecture and in-class activities.

• Lecturer should leave their students around half and one hour to read the module and memorize the main point of the each topic
• Form a group, divide each main topic to every group, present the topic by group
• Do the quiz at end the class

All the lessons learned.

• Definitions of software and software engineering.
• Several software application domain, and its characteristics including the examples– system software, engineering/scientific software, AI software, embedded software, product line, web application and application software
• The Polya’s essence of SE practices – understand the problem, plan a solution, execute the plan and examine the result for accuracy.
• SE principles - The Reason It All Exists; KISS (Keep It Simple, Stupid!); Maintain the Vision; What You Produce, Others Will Consume ; Be Open to the Future; Plan Ahead for Reuse; Think!
•  Software myths have caused serious problems for the software industry. There are three classifications of software myths:
  –Management myths
  –Customer myths
  –Practitioner myths
  

  

  
  
  Muhammad Rijaluddin Bin Mohd Rusli  (IS085739)
  Mohammad Naqib Bin Md Esa                (IS085723)