Job Structure

Job Structure

Introduction

Job structure can be defined as the organization of all the fields of the job, its categories, and the job levels. The job structure of a software engineer consists of a number of responsibilities, duties and fields. The knowledge area of software engineering in particular covers the life cycle of a software, the key activities of the life cycle - from the request of a client to the final decommissioning of the product - and the order in which these activities are performed. It also covers the different people involved: technical sales, engineers, buyers, users, and the director of information systems. According to the SWEBOK key activities of the life cycle of software are: the functional analysis, the architecture, the programming, the tests, the validation, the service and project management.

Discussion

Needs Analysis

Needs analysis is done to collect detailed information on the range of functions that will provide information on software, and the results it will give. Domain knowledge of business software (e.g. banking, industry, administration) facilitates the work of the engineer.

Design

Design is to identify and map the outline of the mechanisms that must be programmed in order to obtain each of the functions that will provide the software. Conceptual plans by software modeling formalisms (UML for example) will be realized. This is also the stage where the use of design patterns software is applied to solve some common designs. The use of the software architecture can also be made (Sarma, 2009).

Building

Building is writing the source code, instructions program that will provide the expected functions, which are the body of software. The programming is performed according to the plans originally established during the design. According to the methodology (e.g., iterative), engineers will return to the stage was drawing to adjust the design to the actual construction.

Tests

A series of audits are conducted by engineers who = detect a maximum of bugs, programming flaws that cause failures or incorrect results. The validation is a review by the client during which it checks that the functions offered by the software to match their expectations and needs.

Maintenance

Analysis operations, programming and testing are done after the software has been made available to users and in which the software undergoes changes, corrections or improvements. The ease of this service will depend on the importance that was given to him during the design phase (Armstrong, 2008).

Project Management

An activity performed throughout the work on the software, which is organizing a team of engineers, assign tasks and monitors the progress of work to finish on schedule. This is a business management also performed in other areas of engineering.

Tools and Methods

Thematic software engineering mainly focus on the tools and methods of specifying features of a software , formal methods ( Method B for example), the tools and methods of software design , design tools, workshop software engineering models Kermeta example, automation of code optimization.

Other areas related to software engineering since they share common tools: formal description of the code, grammars of languages handled. These areas are for example:

the compilation ...