Professional Documents
Culture Documents
Game Documentation
Game Documentation
ABSTRACT:
The methodology of an organization is a social construction that includes the roles, skills,
teaming, activities, deliverables, standards, habits and culture of the organization as it develops software.
We describe a software model checking tool founded on game semantics, highlight the underpinning
theoretical results and discuss several case studies. The tool is based on an interpretation algorithm
defined compositionally on syntax and thus can also handle open programs. Moreover, the models it
produces are equation ally, fully abstract. These features are essential in the modeling and verification of
software components such as modules and turn out to lead to very compact models of programs. The
simplest thing that could possibly work is usually not a framework. Even if it is, developing a
framework is expensive and often fails. But sometimes you do need to develop a framework. Each and
every option are selected by means of mouse pointer. Mouse pointer is internally connected with
processor.
REQUIREMENT ANALYSIS:
Software requirements analysis helps identify the problems a software system should
address and the form solutions might take. Requirements specification identifies an initial mapping of
problems to system-based solutions. The key to success in any project is well-defined and well-
understood requirements. Analyzing and identifying security requirements in light of other system
requirements and business objectives can be challenge. Security requirements introduced into existing
systems or design can result in costly rework or irksome procedures. Evaluating proposed solutions
for cost.Opretional, and technical feasibility is an important element of the requirements analysis. IT
global secure can help your organization make the best management decision possible by developing
and preparing:
. EXISTING SYSTEM:
In this program we use if condition for analysis our result.and using functions for
our number cards.
DESIGN:
SOFTWARE DESIGN is a process of problem-solving and planning for software
solutions. After the purpose and specifications of software is determined; software developers will
design or employ designers to develop a plan for a solution.
Game flow design diagrams are a high-level tool design approach that can compliment
storyboards and provide the detail that storyboards would find more difficult to describe explicity.
It can be partitioned into levels that represent increase in information flow and detailed functionality.
The number of levels in DFD can be increased until every process represents the basic
functionality. As the number of levels gets increased in the DFD, each bubble gets refined.
1. Entity
2. Relationship
3. Attribute.
MODULE DESCRIPTION:
The software to be implemented consists of the following modules:
MODULE-1(FIRST_CARD)
This module works after the execution of first card. It consist set of numbers .If our
number is in first card put 1 for yes otherwise put 0 for no.
MODULE-2(SECOND_CARD)
This module works after the execution of first card. It consist set of numbers .If our
number is in first card put 1 for yes otherwise put 0 for no.
MODULE-3(THIRD_CARD)
This module works after the execution of second card. It consist set of numbers .If our
number is in first card put 1 for yes otherwise put 0 for no.
MODULE-4(FOURTH_CARD)
This module works after the execution of third card. It consist set of numbers .If our
number is in first card put 1 for yes otherwise put 0 for no.
MODULE-5(FIFTH_CARD)
This module works after the execution of fourth card. It consist set of numbers .If our
number is in first card put 1 for yes otherwise put 0 for no.
MODULE-6(SIXTH_CARD)
This module works after the execution of fourth card. It consist set of numbers .If our
number is in first card put 1 for yes otherwise put 0 for no.
MODULE-7(CHECK ANALYSIS)
In this module we check the answer by adding 1,2,4,8,16,32 numbers by choice of their
answer if 1 or 0.
Second_card
Third_card
Fourth_card
Fifth_card
Sixth_card
IMPLEMENTATION:
Implementation is the realization, application, or execution of a plan, idea, model, design,
specification, standard, algorithm, or policy.
The design must be transulated in to a machine-readable form. The code generation step
performs this tasks .If design is performed in a detailed manner, code generation can be accomplished
machanistical.
PROGRAM:
#include<conio.h>
#include<stdio.h>
#include<stdlib.h>
void first_card(void);
void second_card(void);
void third_card(void);
void fourth_card(void);
void fifth_card(void);
void sixth_card(void);
check(void);
void main(void)
{
int ans=0,in=0;
clrscr();
first_card();
in=check();
if(in==0)
{
ans+=1;
}
second_card();
in=check();
if(in==0)
{
ans+=2;
}
third_card();
in=check();
if(in==0)
{
ans+=4;
}
fourth_card();
in=check();
if(in==0)
{
ans+=8;
}
fifth_card();
in=check();
if(in==0)
{
ans+=16;
}
sixth_card();
in=check();
if(in==0)
{
ans+=32;
}
if(ans>60)
{
printf("Enter incorrect number");
}
else
{
printf("your no is: %d",ans);
}
getch();
}
void first_card(void)
{
printf("\t COMPUTERGAME\n\n\n\n");
printf("\t1 \t3 \t5 \t7 \t9 \t11\n\n");
printf("\t13 \t15 \t17 \t19 \t21 \t23 \n\n");
printf("\t25 \t27 \t29 \t31 \t33 \t35 \n\n");
printf("\t37 \t39 \t41 \t43 \t45 \t47 \n\n");
printf("\t49 \t51 \t53 \t55 \t57 \t59 \n\n");
}
void second_card(void)
{
printf("\tCOMPUTERGAME \n\n\n\n");
printf("\t2 \t3 \t6 \t7 \t10 \t11 \n\n");
printf("\t14 \t15 \t18 \t19 \t22 \t23 \n\n");
printf("\t26 \t27 \t30 \t31 \t34 \t35 \n\n");
printf("\t38 \t39 \t42 \t43 \t46 \t47 \n\n");
printf("\t50 \t51 \t54 \t55 \t58 \t59 \n\n");
}
void third_card(void)
{
printf("\tCOMPUTERGAME \n\n\n\n");
printf("\t4 \t5 \t6 \t7 \t12 \t13 \n\n");
printf("\t14 \t15 \t20 \t21 \t22 \t23 \n\n");
printf("\t28 \t29 \t30 \t31 \t36 \t37 \n\n");
printf("\t38 \t39 \t44 \t45 \t46 \t47 \n\n");
printf("\t52 \t53 \t54 \t55 \t60 \t60 \n\n");
}
void fourth_card(void)
{
printf("\tCOMPUTERGAME \n\n\n\n");
printf("\t8 \t9 \t10 \t11 \t12 \t11 \n\n");
printf("\t13 \t14 \t15 \t24 \t25 \t26 \n\n");
printf("\t27 \t28 \t29 \t30 \t31 \t40 \n\n");
printf("\t41 \t42 \t43 \t44 \t45 \t46 \n\n");
printf("\t47 \t56 \t 57 \t58 \t59 \t60 \n\n");
}
void fifth_card()
{
printf("\tCOMPUTERGAME \n\n\n\n");
printf("\t16 \t17 \t18 \t19 \t20 \t21 \n\n");
printf("\t22 \t23 \t24 \t25 \t26 \t27 \n\n");
printf("\t28 \t29 \t30 \t31 \t48 \t49 \n\n");
printf("\t50 \t51 \t52 \t53 \t54 \t55 \n\n");
printf("\t56 \t57 \t58 \t59 \t60 \n\n");
}
void sixth_card()
{
printf("\tCOMPUTERGAME \n\n\n\n");
printf("\t32 \t33 \t34 \t35 \t36 \t37 \n\n");
printf("\t38 \t39 \t40 \t41 \t42 \t43 \n\n");
printf("\t44 \t45 \t46 \t47 \t48 \t49 \n\n");
printf("\t50 \t51 \t52 \t53 \t54 \t55 \n\n");
printf("\t56 \t57 \t58 \t59 \t60 \t60");
}
check(void)
{
int i,index=0;
int value;
printf("please enter \n \t 1------>yes \n \t 0 ------->no");
scanf("%d",&value);
if(value==1)
{
index=0;
}
else
{
index=1;
}
for(i=0;i<=10;i++)
{
printf("\n");
}
return index;
}
TESTING ANALYSIS:
BLACKBOX TESTING:
The black box testing is used to demonstrate that the software functions are operational.
As the name suggests in black box testing it is tested whether the input is accepted properly and output is
correctly produced. The major focus o block box testing is on functions, operations, external interfaces,
external data and information.
WHITEBOX TESTING:
In white box testing the procedural details are closely examined. In this testing the
internals of software are tested to make sure that they operate according to specifications and designs.
Thus major focus of white box testing is on internal structures, logic paths, control flows, data flows,
internal data structures, conditions, loops, etc
Maintenance
In Software engineering ,Software maintenance is the process of enhancing and
optimizing deployed software (software release),as well as remedying defects .Software maintenance is
one of the phases in the software development process, and follows deployment of the software into the
field.
OUTPUT:
Conclusion:
Computer game design is an emerging type of software development activity. Although
early computer games may have required little in the way of game flow design, modern three-
dimensional computer games are becoming increasingly sophisticated, and require a more formalized
design approach. In this article we have described and demonstrated a computer game-flow design
approach that extends and adapts the widely used UML technique of use-case diagrams to make them
more applicable to computer game design.
Softwar
Status e number
User gaming
number Mind Invoke process
User’s techniq
number ue
Read
Coding Check
numbe the
Level 1: rs status
Loadin
g Data
Gaming system
Numb In
ers game
Entity D data store
Info about
Level 2:
Check
Request of reader
&
schedu
le
Entity info Data store
mind mind
Exit Data’s
entity Request in
progra
Requesting data
m
Info
Select
numb Set of number
User er cards
from
card
Select
ed
numb
er
Che
ck Give
Result anal answer
ysis