Implementation of system functionality, Software Engineering

Methodology and system Functionality:

High level views of the proposed system in terms of the requirements that will be supported by the proposed system in the context of business processes and data. This section discusses the various choices and their implications on software and hardware options, methodology selection platforms and testing environments

The functionality of the system will be derived using various techniques and appropriates tools available for analysing the current system where appropriate. The artefacts you produce to model the above will evolve iteratively throughout the development of the system.

B. System design: This section provides an account of the design process in terms of how you:

• applied your chosen method or framework within the project

• designed and evolved the system functional areas;

• Mapped from requirements to prototypes.(should include comprehensive documentation to support the above within the section(normally such documentation should be presented in one or more Appendices)

C. Implementation:

This section describes your implementation in terms of system functionality that has been built and can be shown to be working as expected.

Also contains a section on deployment which describes factors such as :

• System support

• Training

• Data migration from the development environment and/or existing systems to the target environment.

Testing and Evaluation:

This section details the approach taken to test and evaluate the implemented system by making use of a detailed test plan. You need to describe what particular techniques you have used, why you have used these rather than others, and present a summary of your main results. Comprehensive documentation to support testing should be presented in an Appendix.

Evaluation can be approached by measuring and considering the effects of expected outcomes.Or any other project issues which have not been covered in previous sections such as change control, configuration management, risk analysis.

Posted Date: 3/19/2013 6:09:09 AM | Location : United States

Related Discussions:- Implementation of system functionality, Assignment Help, Ask Question on Implementation of system functionality, Get Answer, Expert's Help, Implementation of system functionality Discussions

Write discussion on Implementation of system functionality
Your posts are moderated
Related Questions

Important factors related to library storage operation: It is essential to consider some important factors related to library and information storage and retrieval operations

Differentiate between smoke testing and sanity testing. -Smoke testing verifies all areas of application; sanity testing recognizes one or few areas only. -Smoke testing is

Explain Control Structure Testing Ans) Due to basis path testing alone is insufficient, other methods should be utilized. Condition testing can be utilized to design test cas

Q. Illustrate Basic COCOMO model? Basic COCOMO model:- It provides an order of magnitude of cost. This model utilizes estimated size of software project and the type of softwar

Discuss in details the design steps in transaction mapping. Re-Check the fundamental model. Re-check and refine the DFD for the software. Determine the DFD has either

Define Test Methodology and  Test Scenario Testing methodology verifies how an application will be tested and what will be tested. Example of methodologies: waterfall, agile

The aim of regression testing is to test that the fixes have not formed any other problems elsewhere. The aim is to ensure the software has remained intact. A baseline set of data

When must a function throw an exception? A function must throw an exception when it's not able to fulfil its promise. As soon as function detects a problem which prevents it