early as possible

Upload: hikjsakdnjfvfsdg

Post on 07-Apr-2018

221 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/6/2019 Early as Possible

    1/32

    early as possible.Software willbe tested at everystage and finaltesting will be

    done indummyenvironment.

    Maintenance

  • 8/6/2019 Early as Possible

    2/32

    Deploymentwill

    start after the codeor program is

    appropriatelytested. People are

    oftenresistant tochange and avoidventuring into an

    unfamiliar area,

  • 8/6/2019 Early as Possible

    3/32

    so as a part of

    thedeploymentphase, it is very

    important to havetraining classes

    for new users ofyour software.Maintainingand

    enhancing

  • 8/6/2019 Early as Possible

    4/32

    software to cope

    with newlydiscoveredproble

    msor newrequirements can

    take far more timethan the initialdevelopment of

    the software.It

  • 8/6/2019 Early as Possible

    5/32

    may be

    necessary to addcode that does

    not fit the originaldesign to correct

    anunforeseenproblem or it maybe that a

    customer is

  • 8/6/2019 Early as Possible

    6/32

    requesting more

    functionalityandcode can be

    added toaccommodate

    their requests. Ifthe labor cost ofthe

    maintenancephas

  • 8/6/2019 Early as Possible

    7/32

    e exceeds 25% of

    the prior-phases'labor cost, then it

    is likely that theoverallquality of at

    least one priorphase is poor .Inthat case,

    management

  • 8/6/2019 Early as Possible

    8/32

    should

    consider theoption of

    rebuilding thesystem (or

    portions) beforemaintenance costis out

    of control.Bug

  • 8/6/2019 Early as Possible

    9/32

    Tracking

    Systemtools areoften deployed at

    this stage of theprocess toallow

    developmentteams to interfacewith

    customer/field

  • 8/6/2019 Early as Possible

    10/32

    teams testing the

    software toidentifyany real or

    perceived issues.All aspects of

    softwaredevelopment willbe takencare.

    Industry best

  • 8/6/2019 Early as Possible

    11/32

    practiced Software

    Development LifeCycle (SDLC) will

    be followedtodesign and

    developinternationalstandard product.

  • 8/6/2019 Early as Possible

    12/32

    Chapterisation

    scheme:Following chapter

    schema will befollowed in main

    report. It willsequentiallyrepresentthe

    case/report.

  • 8/6/2019 Early as Possible

    13/32

    (i)

    Chapter-I:Introduction of

    the Problem:This Chapter will

    includebackground of the problem, and what is p

    roposed to be de

  • 8/6/2019 Early as Possible

    14/32

    veloped. Thesign

    ificance of theproblem, the

    objectives and thescope of the

    project andthecontributionand impact by the

    project will be

  • 8/6/2019 Early as Possible

    15/32

    elaborated. A brief

    description of theabout gated

    community wherethe finally project

    willbe implementedwill alsobe

    provided.(ii)

  • 8/6/2019 Early as Possible

    16/32

    Chapter-

    II : TechnologicalPerspective:

    This chapter willinclude anovervie

    w of thetechnologicalconcepts related

    to the project as

  • 8/6/2019 Early as Possible

    17/32

    Radio

    FrequencyIdentification (RFID)

    technology,RelationalD

    atabaseManagementSystem(RDBMS),

    Microsoft Visual

  • 8/6/2019 Early as Possible

    18/32

    Studio (IDE) etc.

    This chapter willalso include

    aboutexistingsoftware

    available in themarket, theirmerit and

    demerit

  • 8/6/2019 Early as Possible

    19/32

    andlimitations/dra

    wbacks ofcurrently available

    solution in themarket.(iii)

    Chapter-III :Methodology:This chapter will

    describe in detail

  • 8/6/2019 Early as Possible

    20/32

    the stepsfollowed

    in completing theproject. All

    aspects ofsoftware

    development willbeconsidered inthis chapter. Full

    description of

  • 8/6/2019 Early as Possible

    21/32

    Software

    Development LifeCycle(SDLC)

    process will bedefined here.(iv)

    Chapter- IVDesign:This chapter will

    describe the detail

  • 8/6/2019 Early as Possible

    22/32

    design of project

    asFlow Chart(FC), Data Flow

    Diagram (DFD),Physical Diagram

    (PD

    ),LogicalDiagram(LD), Flow ofData,

  • 8/6/2019 Early as Possible

    23/32

    Flow of Module

    etc.(v)Chapter- V

    Implementation:This chapter will

    include the finalcoding ofthesoftware and

    documentation of

  • 8/6/2019 Early as Possible

    24/32

    source

    code.Documentation is very

    important

    for

    the purpose offuture

  • 8/6/2019 Early as Possible

    25/32

    maintenance and

    development.Listing of full

    source codewithdocumentation will

    be included asAppendix.(vi)

  • 8/6/2019 Early as Possible

    26/32

    Chapter-

    VI Verification orSoftware testing:

    Verification or Softwaretestingis an

    integral andimportant part ofthe software

    development

  • 8/6/2019 Early as Possible

    27/32

    process.Various t

    esting scenario will be described in

    this chapter andresult will beinclu

    ded asAppendix.(vii)Chapter-

    VII Deployment

  • 8/6/2019 Early as Possible

    28/32

    &

    Maintenance:This chapter will

    describe aboutthevarious

    deploymentscenario andprocedure for

    Access Control

  • 8/6/2019 Early as Possible

    29/32

    System ingated

    community.Maintainability

    aspect will also bedescribed in this

    chapter.Maintainingand enhancingsoftware to cope

    with newly

  • 8/6/2019 Early as Possible

    30/32

    discoveredproble

    msor newrequirements is

    essential for anysoftware

    development.(viii)Chapter- VIISummary:

  • 8/6/2019 Early as Possible

    31/32

    This chapter will

    depict thesummary of the

    projectRadioFrequency

    Identification(RFID) basedAccess Control

    System (ACS) for

  • 8/6/2019 Early as Possible

    32/32

    Gated

    Community.