Software Engineering Portal

Assalamualaikum...

Alhamdulillah...we managed to finish up our project...
This is the url of our SE portal:

www.sep.karnadya.com.my

Thank you...

second presentation

Tomorrow we have second presentation for our group project.present the portal about software engineering subject and sources..good luck for all of you..funtastic six can do it..do your best girls..InsyaAllah

Thank you...

Assalamualaikum and good day...

First of all, I would like to thank our beloved lecturer, Puan Badariah for teaching us Software Engineering subject... She has taught us a lot about this subject... We had learn many things about SE... Thank you, Puan...

Girls... thank you for being cooperative during the project period...:) I wish all of you good luck in final exams... Do your best ok...

Anyway, our second presentation will be on the 23rd of October... I hope that I will do better in the next presentation...huhuhu... I'll try my best to do the best...

Our portal is still in progress.... InsyaALLAH we will be able to finish it up before Hari Raya break...So that, all of us can enjoy our Hari Raya...hehehe....

By the way... I think this is the last post from me...since Puan Badariah will count all the posts starting from the beginning of the sem until today... I hope that we will be able to get good marks for this assignment since we are one of the group with the highest total number of posts...:)

Since this is my last post, I would like to apologize to all of you, if I said or did anything that hurt your feelings... I apologize for all the mistakes i've done...

Lastly... Selamat Hari Raya Aidilfitri to everyone...
Maaf Zahir dan Batin....
from me, Laila Hana...and the rest of the member of funtastic six...Kak Nor, Wani, Wawa, Nano and Mumtaz...

All the best to you guys...:) Take care...

TESTING VS PROVING

In proving a program correct, the test team or programmer considers only the code and its input and output conditions. The program is viewed in terms of the classes of data and conditions described in the design. Thus, the proof may not involve executing the code but rather understanding what is going on inside the program.

Customers have a different point of view. To demonstrate to them that a program is working properly, we must show them how the code performs from outside the program. In this sense, testing become a basis for deciding how the program will behave in a given situation.

Whereas a proof tells us how a program will work in a hypothetical environment described by the design and requirements, testing gives us information about how a program works in its actual operating environment.

Web Portal in Progress

For about 3 weeks earlier, we started making the web portal. Interface, overall elements and attributes need to be considered as referred to the user requirement that should be contained in the expected web portal, we were having a few meetings from time to time, discussing what should have and what should not, inserting files and document.

We were basically done with the layout, generally the interface, buttons and links. The interface will be simple as it will make the page process go more smoothly. The navigation buttons will help users to navigate around and will have easy access to view the portal as well.

The whole system will be developed using CSS. The database will be developed using PhP. However, we were having some difficulties on it, but we were trying to do our best in doing this web portal as expected by the user.

As for present, we just finished uploaded a few things expected by the user, calendar; Allow users to make appointments with the administrator besides able to look at the date of the day and search engine; User type the keyword in the search engine box and than enter -> The page searches the keyword at the database -> Database sends the information about the keyword -> Exit.

What to be done for upcoming days, user log in and just about a few more things to be inserted in the web portal, and we were done with it.

*That is all for the progression of our web portal at the moment.

*Progression will be informed from time to time :)

Format for Final Exam Paper...

Assalamualaikum and good evening....

Girls... as a reminder, this is the format of the final exam paper for Software Engineering...
Our lecturer, Puan Badariah told us about the exam format in our last class...which was on Tuesday...

There will be 3 sections in the final exam :

Section A (16 q) - Fill in the blanks ( 20 blanks) - 20 marks
Section B (7 q) - Short answers (differentiate, lists, draw, definition ) - 50 marks
Section C (2 q) - Understanding, memory recall, C codes - 15 marks

Don't forget to put examples for the questions that require detail explainations...

So,girls... please be prepared for the final examination paper which will be held one week after our Hari Raya break...

Thank you...

Last lecture..

Chapter 11 : Maintaining the System

11.1 The Changing System
Maintenance: any work done to change the system after it is in operation.
Software does not degrade or require periodic maintenance.
Lehman’s System Types :
1. S-system: formally defined, derivable from a specification.
2. P-system: requirements based on approximate solution to a problem, but real-
world remains stable.
3. E-system: embedded in the real world and changes as the world does.

11.2 The Nature of Maintenance
Types of Maintenance :
1. Corrective: maintaining control over day-to-day functions.
2. Adaptive: maintaining control over system modifications.
3. Perfective: perfecting existing functions.
4. Preventive: preventing system performance from degrading to unacceptable
levels.
Who Performs Maintenance :
1. Separate maintenance team
2. Part of development team.

11.3 Maintenance Problems
· Staff problems: Limited understanding, management priorities and morale.
· Technical problems: Artifacts and paradigms and testing difficulties.

11.4 Measuring Maintenance Characteristics : Maintainability is not only restricted to code, but also including specification, design, and test plan documentations. Maintainability can be viewed in two ways, either external view of the software or internal view of the software.

11.5 Maintenance Techniques and Tools
· Configuration management
– Configuration control board
– Change control
· Impact analysis
· Automated maintenance tools

11.6 Software Rejuvenation
1. Redocumentation: static analysis adds more information.
2. Restructuring: transform to improve code structure.
3. Reverse engineering: recreate design and specification information from the code.
4. Reengineering: reverse engineer and then make changes to specification and design
to complete the logical model; then generate new system from revised specification
and design

11.7 Information System Example
Piccadilly System
- The software can not be an S-system.
- The software can not be a P-system.
- The software must be E-system.

11.8 Real Time Example : Developers focused on mitigating random failure. The inertial reference system failed because of a design fault, not a result of a random failure. Needs to change the failure strategy and implement a series of preventive enhancements. Invokes change control and configuration management