Systems development life-cycle Dr. Redekopp & Dr Kalanda

systems development life cycle (SDLC) The systems development life cycle (SDLC) in software engineering, is a process of creating or altering information systems, and the models and methodologies that people use to develop these systems. In software engineering, the SDLC concept underpins many kinds of software development methodologies. These methodologies form the framework for planning and controlling the creation of an information system.

Planning Planning is an objective of each and every activity, where we want to discover things that belong to the project. An important task in creating a software program is extracting the requirements or requirements analysis. Customers Generally have an abstract idea of what they want as an end result, but do not know what software should do. Skilled and experienced software engineers recognize incomplete, ambiguous, or even contradictory requirements at this point.

Implementation, testing and documenting Implementation is the part of the process where software engineers actually program the code for the project. Software testing is an integral and important phase of the software development process. This part of the process ensures that defects are recognized as soon as possible. Documenting the internal design of software for the purpose of future maintenance and enhancement is done throughout development

Deployment and maintenance Deployment starts directly after the code is appropriately tested, approved for release, and sold or otherwise distributed into a production environment. This may involve installation, customization (such as by setting parameters to the customer's values), testing, and possibly an extended period of evaluation. Software training and support is important, as software is only effective if it is used correctly. Maintaining and enhancing software to cope with newly discovered faults or requirements can take substantial time and effort, as missed requirements may force redesign of the software

Game Development Lifecycle If you are the type of person that likes to get down and dirty and just code till it works, here is where you differ from the type of person that likes to have a requirements, or even functional document before writing code.

The Cycle I've most recently tried This is the Cycle I've most recently tried to adopt. 1) Initial idea developed 2) Functional requirements documented 3) Story/script created 4) Non-function requirements documented 5) Research on what’ll be needed 6) Technical documentation created 7) Licensing of required technology 8) Coding and asset creation 9) Coding and asset integration 10) Quality assurance 11) Sales and Marketing 12) Distribution

Initial idea developed initial ideas are simple ideas that you thought of at the start of the project.

Functional Specification In systems engineering a functional specification is a document that clearly and accurately describes the essential technical requirements for items, materials, or services including the procedures by which it can be determined that the requirements have been met.

The game design team The game design team usually have a basic document that one or two of them might have created with a game idea. All of the designers on the project, along with the lead designer, discuss the concept of the game like what it is about and the type of gameplay. From this meeting, or a series of meetings, the Game Design Document (GDD)is fleshed out, at least to a point where there is a very good feel for the game even though this is not the final.

Game Genres Like cinema, computer games have as many different genre categories as they do audience groups. Unlike cinema, many of them are known by their tongue- twisting acronyms! Here are some of the most notable:

Educational Games: games are designed to help users increase their cognitive functioning, often through entertaining mini-games, logic exercises, and daily or weekly tests. Activities typically involve math, language, concentration, reading comprehension, and memory skills, and educational games also tend to keep track of progress so players can see how they've improved over the course of time. Advergames: Games developed for advertising purposes. Adventure: Adventure games involve exploration of, and interaction with, the environment as a main facet of gameplay. Story and puzzle solving are also highlighted and interaction is usually driven by point and click. Fighting plays a minor role. Adventure games include Zork and Myst. Game Genres

Classic Arcade: Classic arcade games refer to games that originally existed on freestanding coin-operated machines. Classic arcade games include Pong and Space Invaders Fighting: Fighting games involves rendering opponents unconscious or dead by using a number of different moves. Gameplay tactics are limited to selecting the most appropriate move in a situation. Fighting games include Tekken 3 and Street Fighter. Puzzle: Puzzle games are short but addictive graphical games that usually require the player to solve a puzzle such as a maze, logical problem or positioning different pieces together. Puzzle games include Tetris and Bust A Move (Puzzle Bobble) Game Genres

Racing Games: Racing games involve the player competing in races. Racing games include Daytona and the Mario Kart series. Strategy Games: Strategy games require the player to take on a leadership role and oversee every detail of the provided scenario(s). Gameplay focuses on strategies and careful planning and resource management in order to win. Strategy games include Age of Mythology. Simulations: Simulation games attempt to realistically mimic conditions of a particular environment or activity. Sim games include SimCity and Flight emulators. Sports Games: Sports Games emulate traditional physical sports such as basketball and golf. Web based games: Web based games are those available via the web and are usually developed in Flash or Shockwave. Game Genres

Let us Play