28-08-2009, 02:31 AM
1.4 Methodology
The method being used in developing the system is the system Development Life Cycle (SDLC) The SDLC process includes project identification and selection, project initiation and planning, analysis, design, implementation and maintenance.
1.4.1 System Development Life Cycle (SDLC)
The system Development Life Cycle(SDLC) is a traditional methodology used to develop, maintain and replace or enhance information system. The main reason SDLC model is chosen because in SDLC it is possible to complete some activities in one phase in parallel with some activities of another phase. The life cycle can also be interactive that is phase are repeated as required until an acceptable system is found.
1.4.1.1 Phase 1: Project identification and selection
In this phase the project information system needs are identified and analyzed such as identified the title of the project that is Network Sniffer and Connection Analyzer, scope and objective of the Network Sniffer and Connection Analyzer.
Network Sniffer and Connection Analyzer
1.4.1.2 Phase 2: Project initiation and planning
During this phase the Gantt chart has been developed as a time line to determining the task involve in developing the Network Sniffer and Connection Analyzer.
1.4.1.3 Phase 3: Analysis
In the phase, the exiting system is studies by collecting the information through the Internet and analyzed the information to get alternatives for the used of proposed system. Determine what the Network Sniffer and Connection Analyzer should do.
1.4.1.4 Phase 4: Design
Logical design is the fourth phase in SDLC methodology. The functional features chosen for the proposed system in Analysis phase are described. Part of the logical design of the information system is to devise the user interface. The interface plays an important role to connect the user with the system and is thus extremely important.
1.5 Conclusion
As the conclusion, the profiles of three existing systems are shown to produce a better system than the other. Stating the information provided to determine the advantages and disadvantages of each system has showed the comparison between them and the proposed system. The readers will to know the differences between the existing systems compared to the proposed system.
SYSTEM ANALYSIS
2.0 Introduction
The purpose of system analysis is to know the system requirement and specification before system development start. It is very import because the developer will get a clear view of the system that is going to be developed. It is also to increase productivity by making less error because of careful planning.
The Scope in this chapter will cover the system requirement of the system. This is really important because a developer have to know the requirement of the system first, without knowing the requirement it would be likely that developer will make a lot of mistake and the proposed system may not follow the requirement needed to run the software. Process modeling, logic modeling and concept modeling will also included in this chapter.
2.1 Determining System Requirement
In determining system requirement, the hardware and software requirement aspect will be given priority. This will include the external interface requirement and user requirement. By determining these requirement the scope of the proposed system can be determine and also provide a guidelines for the developer.
2.1.1 External Interface requirement
The external interface requirement based on user, hardware and software requirement .it will ensure to produce a better human computer interaction. Here are the requirements stated below:
2.1.1.1 User Requirement
A user requirement can be defined as an in-depth study of end user information needs that produce functional requirement that are used as he basic for the design of proposed system.
Portability
The system must be portable to use in different type of operating system. The System must be applicable to all programs and support all devices.
Reliability
The system must be reliable in terms of usability. This application should be able to deliver consistent and accurate data for user. The users shouldnâ„¢t get any type error of the message or incomplete interface when using this system
Efficiency
This programs efficiency will vastly depend on the memory, display and the processing speed .So the minimum requirement id taken to develop it very efficient.
2.1.1.2 Hardware requirement
Below are minimal requirement for the user to run the system.
Processor: Pentium 133MHz
Hard disk: 2.1GB
Internet Explorer
Keyboard
Mouse
Monitor
Printer
2.1.1.3 Software requirement
Asp.net is requirement for developing the Application.
2.1.2 Functional Requirement
Functional requirement provides a clear view on the input, information that will be processed and output of the system. This is to ensure the functionality of the system will meet the goal that has been stated:
Project Feasibility
Before the start of the real work to ascertain the likelihood of the projects success, a preliminary study undertaken is feasibility study. Feasibility study is an analysis of all possible solutions to a problem and a recommendation the best solution to use. It involves evaluating how the solution will fit into the proposed project or corporation.
The analysis of a problem is to conclude whether it can be solved effectively or not. The schedule, Operational, Technical and Economical are the part of the study. Results of which provides the pros & cons of the solution. If unlimited resources and infinite time is available, all the projects are feasible. But the development of computer- based system is likely to be played by scarcity of resources and difficulty in the duration of completion time. The duration of computer “ based can be studied in three major areas
Before proceeding to any further phase in developing, the feasibility of this project has to be studied to ensure its:
§ Schedule feasibility
§ Economic feasibility
§ Technical feasibility
§ Operational feasibility
Schedule feasibility
For this current developing project, a period time of 6 months was given to me to accomplish the project. Subsequence this project has the option to carry on until the next phase. For the first phase, all the initiation and determination on the problem area and solution will be stated out, a clear report will be produced. For the second phase, development and coding for the suggested automation system will be implemented, test run and install if permission is granted. However, for the prediction, if this project had failed to meet it objective and solved the problem, this project will be withdrawn from the current process. All the progress and process will be halted for further inspection.
Economic feasibility
According to Richard Fairly, Author of Software Engineering Concepts, the process of identifying the financial benefit and costs associated with the development of the project will be initiated to determine whatever this project has the value and the tangible and intangible benefits. Cost and benefits for this project will be outline clearly for references. For most of the systems generally the Economic feasibility is considered at bottom line. It is a fact that computerization of the project is economically beneficial. To achieve the necessary results it will increase the efficiency and decrease the man “ hour required. It will provide up-to-date and timely management to the administrative and individual departments. The system performance will be increased with information available in a few seconds. The economic feasibility study should demonstrate the benefits of the proposed project developer Basically, the cost of the overall project is divided into 2 categories:
(i) Cost Prediction
(ii) Benefits Prediction
(i) Cost Prediction
Developing Cost “ The cost that are required to develop the current project such as personal cost, computer usage, training, administrative cost, purchase or hardware, software and tools to run the project.
Operating Cost - Divide into fixed cost and variable cost. Fixed cost usually included lease payment, software license and salary. For variable cost, it involved the computer usage, supplies and prorated overhead cost: electricity, network bill etc.
By apply the project, there are several expected benefit based on our experience and prediction:
(ii) Benefits Prediction
Tangible Benefits
Cost reduction and avoidance.
Error reduction.
Increased flexibility
Increased the speed of daily business progress.
Increasing sale opportunities.
Intangible Benefits
Faster decision making on reservation and availability of facilities.
Improved customer goodwill due to fast and correct service.
Improved work process and employee morale.
Better service to community.
A cost benefits analysis was done base on the usage of resources
Cost Benefit Analysis
System Development Cost
Development
Ø2 System Analysis and Requirement Determination
Ø3 System Design
Ø4 Development and Implementation
Ø5 Consultation Fees
Equipment Purchase
Ø1 Require component and unit (Computer software & hardware)
Ø2 Require furniture
Ø3 Location Preparation
Ø4 Total Development Cost
System Operating Cost include:
Program maintenance
Additional Equipment Maintenance
Total Operating Cost (Annual)
Total Investment = Total Operating Cost + Total Development Cost
Expected Life-time = 10 years
System Benefits
Tangible Benefits
Saving On additional working staff or personal payment
Operating Savings
Intangible Benefits
Faster decision making on reservation and availability of facilities.
Improved customer goodwill due to fast and correct service.
Improved work process and employee morale.
Improved work process and employee morale.
Above are the benefits that canâ„¢t be measured by figure, but for sure the there will be an great incremental of goodwill.
Return On Investment (ROI)
ROI= Lifetime benefits -- Lifetime Cost
Life Time Cost
© Technical feasibility
From what I had survey and observe, I found out that the current proposed solution can adapt to the current requirement. The solution, to the existing problem for Online Reservation system, can be provided using divergent paths of tools and techniques. Lot of ideas is generated from database end to front end but each of them deemed to be feasible in technical perspective. The entire requirement is mostly computer and Internet service provider and minor reconstruction for the arrangement of tools and devices. Still, since most of the operating personal is not computer literate, so training on how to manage and operate the purposed system will be inserted in the implementation.
(d) Operational Feasibility:
The current existing system is less interactive and not up to the mark in terms of customer support. From all these, we can conclude that this system is Economically, Technically and functionally feasible. With the new system that we are going to develop, you can improve online transaction. And the system has to be design in such a way to extend further.
The purposed system and application will apply the GUI (Graphic User Interface) concept and the navigation of the system and application will be the standard input device that is the mouse and keyboard. For future enhancement, SMS, Online payment will be included for proposed online system. will be implemented if Oman Air authority able to expand its area and business progress to a higher level. As mention before, the staff and related operate personal will be trained by the developer or the personal in charge so they can adapt to the new system and environment
2.2.1 Context Diagram
The major objective of a context diagram is to provide a graphical representation of the whole system. As I stated earlier it consists of all the system boundaries, all the external entities that interact with the system and major data flow between the entities in the system. Refer to the following diagram.
2.2.2 Data Flow Diagram
Data flow diagram will act as a graphical representation of the system in terms of interaction between the system, external entities, and process and how data stored in certain location.
External entities
Data stores
Process
Data Flow
Refer to the following diagrams for level-o and level -1
Figure 2.2 below shows the level-1 DFD for login Authentication process. This sub process from level O DFD will focus on authenticating and validating both the administrator. It receives userâ„¢s login information as input and depending on the type of the users; the process will direct the user to either the administrator main page.
D1 Connection s
D2 Tcp/udp
D3 PackitInfo
Admin
Login
Info
2.3 Flow Chart
A flow chart illustrates the relation between processes. By visualizing the process, a flow chart can quickly help the bottlenecks or inefficiencies where the process can be improved.
Admin
Admin
Yes
No
Figure 2.7 Flow Chat
