Link to our portal

http://funsoften07.clanteam.com/

Presentation

Tommorrow is our group presentation to present our blog. Hopefully our blog have gave some interest to you with our latest information. Gud luck for presentation tommorrow.

Exercise on Calculating the Path

Path Formular

Example

Based on the diagram 1, the red color (dots) that has been labeled is representing the nodes, while the normal black color (line) is representing edges.

How to calculate

1. Identify and total up the nodes. N = 6 nodes.
2. Next identify and total up the edges. E = 8 edges/paths.
3. Apply the formular.

CC = E - N + 2

CC = 8 - 6 + 2

CC = 4.

How to find Length( Path )

Based on the diagram 1, we can find path at 4 or more length.

Path with 4 length:-

1. A - I
2. A - B - C - D
3. A -B - X -D
4. A - C ...

_________________

1. A - B - C - D - I
2. A ....

The path that has been selected can't be taken twice. So we will add the next path as (...), for example path(length) at no 4.

If 'A' has been chosen as the first starting point, the next path(length) also need to start with 'A'.

QUIZ (6/9/07)

Last week, on Thursday (6/9/2007), we had a quiz based on chapter 8. This quiz is based on our knowledge whether we had read chapter 8 or not, because there is no lecture on chapter 8 in class yet on that day.There are 3 questions;

Question 1
List 4 types of faults.

Answer
1)Algorithmic fault
2)Computation and precision fault
3)Documentation fault
4)Performance fault

Question 2
Who performs testing and why?

Answer
Independent test team
A team that performs most of system and launch testing independently from the teams that developed the system or application to;
-avoid conflict
-improve objectivity
-allow testing and coding concurrently

Question 3
List 2 types of testing and briefly explain.

Answer
1)Bottom-up
- Technique of integration testing. It is also the sequence of tests and their dependencies.
Example:



2) Big-bang
- Requires both stubs and drivers to test the independent components.
Example:

Final Examination Formats.

Final Examination.

There consist of three(3) section:-

A. Fill in the blank Question.

• Matching (20 marks) - 20 questions with 40 choices of answer to be matched.

B. Short answer.

• Structure question (50 marks) - 7 to 8 questions.
• Type of question (will be asked) : explain briefly, explain, list and give examples.
• 3 selected : explain briefly, explain, list.
• From above[3 selected]: focus on the definition, the detail and give the example).

C. Synthesis (Combination number of formats).

• Consist two sub - question. (30 marks) - 3 questions. :-

a) Drawing diagrams / models. - examples WBS, chart..etc.

b) General / opinion. - examples You have promoted a job Nuclear System Company, Do you want to take the job or not and please state why? [Note: There is no write or wrong question, just simply an expression of your physicological thinking about software engineering course.]

So Good luck For the final Guys & Girls ~_^\

Exercise on Use-Case and Statechart/ State Transition Diagram

Class Exercise with Puan Badariah

On the thursday(week 6)'s class we have done an exercise about Use-cases and Statechart in one of the subtopic in chapter 4. From that session, we as the student of S.E get to know more futhter about use-case characteristics such as use-case consist of an actor(s), use-case(oval shape- represent as a process), and interaction(arrow ->/<-).

Figure 1 : Show the characteristics of Use-Case.

In conclusion, we find that the use-cases is much more different from DFD(data flow diagram) not just from entire physical looks but also from interior that is use-cases can hide its details while the DFD types can view/show the details.

USE CASE DIAGRAM

Hi.. everyone. Hopefully all of u are happy yesterday because we got some knowledge about "use case" diagram. Use case diagram is used to present how a system flow by presented 3 item to show connections in the system. Actually i 'm was interested in learning this diagram because it look simple as long as we know how to find out the 3 items which is: 1)Actor 2)use case and 3)interaction/association. Here i have descriptions of that 3 item.. :)..

Use cases. A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse.

Actors. An actor is a person, organization, or external system that plays a role in one or more interactions with your system. Actors are drawn as stick figures.

Associations. Associations between actors and use cases are indicated in use case diagrams by solid lines. An association exists whenever an actor is involved with an interaction described by a use case. Associations are modeled as lines connecting use cases and actors to one another, with an optional arrowhead on one end of the line. The arrowhead is often used to indicating the direction of the initial invocation of the relationship or to indicate the primary actor within the use case. The arrowheads are typically confused with data flow and as a result I avoid their use.

System boundary boxes (optional). We can draw a rectangle around the use cases, called the system boundary box, to indicates the scope of your system. Anything within the box represents functionality that is in scope and anything outside the box is not. System boundary boxes are rarely used, although on occasion we have used them to identify which use cases will be delivered in each major release of a system.