Webpage Design Information System Project Management Report

This report details the development of a web application, addressing the project's requirements, design, and management. It begins with the author's role as an Application Developer at ABC Group and the initial idea from the Lead Engineer. The report then explores project management information systems and the Agile project management methodology, outlining its features and steps. It details the assessment of requirements, including identifying needs, gathering ideas, and feasibility testing. The report further describes the organizational and process aspects of the final solution, including the design phase (high and low-level design), implementation, testing, documentation, deployment, and maintenance. The references cited provide additional context for the project's methodologies and frameworks.

Webpage Design
Information System Project Management
Student Name –
Student ID –

Contents
Background............................................................................................................................................3
Literature Survey...................................................................................................................................3
Agile Project Management....................................................................................................................3
Assessment of the requirement............................................................................................................4
Organisation and Process for final solution...........................................................................................5
References.............................................................................................................................................6

Background
I have been appointed the role of Application Developer at ABC Group. The Lead
Engineer in Quality came to me with an idea to develop a software application. We
have to develop a solution. I have to design the methodology for this software
application development. We have to systematically design the steps to develop a
software application n an efficient manner.
Literature Survey
Project Management Information Systems are designed to provide support to the
project management ( Kostalova et al, 2015 ). In project management, various steps
are needed which range from proposal of an idea to the final delivery of the software
to the customer. A coherent type of framework is better to understand how successful
an information system project is (Putra et al, 2016 ). This framework has been studied
in detail.
Agile Project Management
Features of Agile Project Management
Agile project management has the following features: A vision, it starts in a broad
way, learning and adapting – as per conditions, movement towards the target in
increments, continuous cycle, small and highly efficient teams and customer
involvement. In Agile project management, we keep on iterating the process till all
the steps are validated.

Steps of Agile Project Management
The various steps involved in agile project management are : Requirements, Plan,
Design, Develop, Release, Track and Monitor, Methodology, Discussion – the
product owner will meet the sales team, Analysis – the requirements are analysed,
Strategy – a strategy is set, Execution – the plan is executed, QA (Quality Assurance)
and Testing – to check the quality.
Implementation
To implement our method, the steps are: develop functionality 1, Integrate and Test,
develop functionality 2, Integrate and Test, develop functionality 3, Integrate and
Test, and so on till develop functionality N, Integrate and Test.
Then, we have Demo Release, Client’s feedback, Making relevant changes and
system testing.
If all functionalities complete, we can proceed else, we go to the next iteration.
Assessment of the requirement
We have the following steps: Identify the need, develop the ideas of software product,
collect the ideas from the customers, staff or creative people, to test the ideas if they
are economically feasible, to test the ideas as per time and cost factors ( done by the
Marketing and Development team). This is the main step in the planning process as a
major decision is made in this step.
Requirement Analysis

It is done to find out the things which are needed in the project, Software engineers
with skills and experience needed and also to design the scope document ( mentioning
the area of development clearly ).
Organisation and Process for final solution
Designing Phase
In software design, the design of software is generated. A higher level design – a big picture
of the project is presented next. Then, a decision about the computer language and operating
system used and hardware required is made. Then, a lower level design – which defines sub
parts of high level design is designed. If a high level design is divided into small low level
designs, then it becomes easier to implement small modules rather than designing complete
design in 1 go. This can be divided amongst the developing team for efficient design.
Implement, Test and Document
The program code is designed by the software engineers to implement the project.
The software is then tested to find any errors or defects. Documentation is done for
the detailed design of the software. This is done for future security and by a team
dedicated for developing. Agile model needs lesser documentation.
Deploy and Maintain

Once the code is tested and then release after the approval, it is sold to the customers.
Installing, customizing and testing is then required. Training and support needs to be
provided. In case of any faulty operation, maintenance is required. A proper training
and future support will ensure a positive publicity of the software developed and
make it popular among the masses.
References
Kostalova, J., Tetrevova, L. and Svedik, J., 2015. Support of project management
methods by project management information system. Procedia-Social and Behavioral
Sciences, 210, pp.96-104.
Putra, S.J., Ahlan, A.R. and Kartiwi, M., 2016. A coherent framework for
understanding the success of an information system project.