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

CASE TOOL For reverse engineering

here some information on reverse engineering CASE TOOL (InSight Tool):
http://ieeexplore.ieee.org/iel5/6783/18169/00841062.pdf

Definition of Software Engineering

Software Engineering has come to mean at least two different things in our industry. First of all the term "software engineer" has generally replaced the term "programmer". So, in that sense there is a tendency to extrapolate in people's minds that Software Engineering is merely the act of programming. Secondly, the term "Software Engineering" has been used to describe "building of software systems which are so large or so complex that they are built by a team or teams of engineers. Yet, there is increasing evidence that many of the processes we have been developing for large groups of engineers also apply to the best practices of even individual engineers.
Software Engineering is intended to mean the best-practice processes used to create and or maintain software, whether for groups or individuals, in attempt to rid ourselves of the usual haphazard methods that have plagued the software industry. This would include subjects like Configuration Management, Project Planning, Project Tracking, Software Quality Assurance, Risk Management, Formal Inspections, etc.

** extra knowlegde for everybody**

what web portal means?...

Portal

Web access point. A portal consists of web pages that act as a starting point for using the Web or web-based services. The word was first used to describe the sites of popular Internet access providers or search engines such as AOL, MSN and Yahoo! Later on, it was extended into the world of work, where a corporate portal or enterprise information portal acts as a starting point for employees or associates of an organization to access corporate information and applications. Portal software has become a distinct class of web server software that acts as a platform for deploying portals.

-Just for extra knowledge for everybody-

Chapter 10 : Delivering the System

This is for up coming lecture...

Delivering the System is more than just putting the system in place.It is also helping users to understand and feel comfortable with the system training and documentation.

10.1 Training

• Types of People Who Use a System
• User and Operator Functions
• Types of Training
• Training Aids
• Guidelines for Training

10.2 Documentation

• Considering the Audiences
• Types of Documentations
• User Helps and Troubleshooting
• Guidelines for Failure Messages

10.3 Information System Example

• Piccadilly System

10.4 Real Time Example

• Ariane-5

10.5 What this Chapter Means for You

Training and documentation should be planned and tracked from the project’s beginning. Training and documentation software should be integrated with the regular system software. All training and documentation modules and documents should take into account the varying needs of different audiences.