before information system is developed, usually beforehand begun with existence a insident and that system development planning. without good system design existence, system development will not such as those which supposed. system design is guide to do system development.
system wisdom
wisdom to develop information system is done by management top, because management wishes for to reaches chances existing unachievable by old ones system or has many weaknesses necessary at improve. for example, some years ago management from mckenson decide wisdom to apply a system design to develop inwrought information system to increase productivity from employees.
system design
after top management decides wisdom to develop information system, before that system is at develops, so necessary planned beforehand. system design concerns estimation from physical needs, worker, and cost that wanted to support from system development. system design usually handled by staff system designer, if staff this is there is no, so planning can be done by system department.
- planning staff has task to do system design based on system wisdom that appointed by management top. when staff this there is no, so the function will be taken to displace by department system developers.
- has task to develop system as according to plan that made ole planning staff and when does this there is no, the function will be taken to displace by system developers consultant outside company.
- has task to operate system that developed by system developers department
system design process
system design process can be grouped to into three principal process, that is:
- plan system projects that done by system designer staff.
- will determine system projects that be developed that done by director committee.
- define system projects that developed by systems analysis.
stages plan system project:
1. determine aim, planning with tactics companies.
2. identify system projects
3. decide system projects target
4. decide system projects obstacle
5. menetu system projects priority.
6. make system design report.
will prepare system projects that be developed
1. indicate team analysis
2. announce system developers project
define system projects that developed
thereby task that must be done by team analysis in this stage:
1. identify to return scope and system project target,
2. do feasibility study,
3. evaluate system project feasibility,
4. make project proposal,
5. ask management sanctions.
do feasibility study
feasibility study a study that be used to menetu is system development proper at go on
or at stop. this watchfulness aims unuk:
1. realize operation from old ones system
2. determine system user needs marginally to can achieve these system target.
3. determine troubleshoots that so that old ones system not yet can achieve aim.
evaluate system project feasibility
five feasibility that can considering:
1. technique feasibility
2. operation feasibility
3. schedule feasibility
4. economy feasibility
5. law feasibility
Minggu, 29 Maret 2009
Minggu, 08 Maret 2009
Destination Information System Development
Important matter from system development :
• Because problems of the long system, the problem be appear is :
- crummy Settled of the long system because the long system can’t operate with good. Many fraudulent with expressly that result , it’s make money firm not safe.
- Not intentional the wrong can cause truth from data less
- Don’t the efficient data
- Don’t the loyal with firm
• Development organization
Between is information more and more extensive, data volume more increase, principle change new accountancy. Because it change, then the long system not effective again.
• For reaches to chances
Because with development system information, organization can take decision swiftly and make sever by quick.
• existence Instructions (directives) from leadership, for example government regulation
Destination from information system development
• for make easy organization in break problem
• to make easy to get to chances existing
• to make easy to finish existing instructions
by applying information system, hope from a organization as following :
• performance
this measured from reduction and efficient time.
• information
this measured to make easy give information and easy information service.
• economy
with the new system information, hope organization is decrease cost for operation firm.
• Control
With the new system information, hope organization is make easy in detect and repair error from long system.
• Efficiency
Example : Decrease time for do a job in organization
• Services
It is destination fro increase from service system.
Principle from information system development
• System for management
Destination for make easy regulate organization from a firm
• System is big investment
Investigation all alternative(minimize opportunity cost the lost)
• System wants one who educated, not educate formal
• System development have to not massage, can done at random
• Don’t be afraid cancel project, it destination to avoid loss from a organization.
• System documentation, it destination to make easy to see from a system existing
System development life cycle
• life cycle model waterfall a method system the working gradually, in every stage can not return previous step. The step composition is requirements, design, implementation, verification, maintenance. With waterfall method, if step be verification we can’t previous to step design.
• life cycle with method itratif, by using this method our first does with initial planning, then requirement, analysis and design, then implementation, deployment, besides deployment we also do testing, then continued with evaluation. if there deficit or error in system, we can do new planning. this be difference between method waterfall with itratif. itratif can do change if there error in system.
• from life cycle spiral model, first step at does in spiral method concept of requirement that present in stage development, then concept of operation this present in stage plan, stage requirement plan that present in stage determine, risk analysis this present in stage identfy and resolve risk, get a temporary result then that is continued with stage venfication and validation, then development plan, risk analysis, produce a prototype 2, then at continue with venfication and validation, then at continue with test plan, continued again with risk analysis and produce oprational prototype, continued with detailed design, code, integration, test, implementation, and last is done release from system made.
approaches of developing a system
• will approach classic opponent will approach structured will approach this will emphasized that system development success when follow stage at system life cycle.
- pendekatan classic approach in system development that follow stages at system life cycle without supplied with tools and techniques memadai.
- pendekatan structured approach this that begun from beginning year 1970 called with approach structured. approach structured equiped with tools and techniques that wanted in system development so that end result from system that developed be got system so that end result from system the structure will be be defined well and clear.
• approach pieces opponent approaches system.
approach pieces be to approach system development that emphasized at one particular activity or certain application. approach system that pay attention information system as one integration unitary to each activity or the application.
• approach system comprehensive opponent approaches
approach sistem-menyeluruh be to approach menyang system together according to comprehensive. will approach this less synchronized for system complex because difficult to be developed. this be to approach classic approach modulate try broken complex system become some part or simple module, so that system easier will be understood and developed.
• approach opponent far jump approaches to bloom.
approach to jump -jauh apply change according to together use sophisticated technology. this change is many contains risk, because computer technology so fast bloom and to year coming be worn out. approach this too expensive, because need investment at the same moment. approach to bloom to apply sophisticated technology just for applications that need at that moment and then be developed for periods next will follow the need as according to existing technology development
meaning of methodology, method and algorithm
• methodology is unitary from methods, procedures, job concepts, rules that used by a science, art, or discipline the other
• method is a steps to in methodology
• algorithm is sequence procedure to break problem.
three classifications of development methodology
• functional decomposition methodologies
this methodology constitute in solution from system into sub system smaller. belong into group methodologies this:
- HIPO (hierarchy plus-process-output)
- Stepwise refinement (SR) or iterative stepwise refinement(ISR)
- Information-hiding
• Data oriented methodologies
- Data flow methodologies
this methodology is in general is based in solution from system intoes modules based on from type element data and module logic behaviour in system
- Data structure oriented methodologies
this methodology emphasizeds structure from input and output at system. mask in this methodology: jsd (jakson's systems development) and w/o(warnier/orr)
tools for developing a system
• system development tool:
HIPO diagram, used in metodelogi HIPO
Data flow diagram, used in system analysis and design S
Structured chart, used at method wanier/orr
Jakson's diagram, used at methodology jakson's system development
Techniques used in developing a system
techniques that can be used :
• technique management project, that is CPM(critical part method) and PERT (program evaluation and review technique). This technique used in project scheduling.
• Fact finding techniques, that is technique that can be used to gather fact and find data in activity study existing activity.
• technique analysis cost/benefit (cost-effectiveness analisys or cost-benefit analysis)
• technique to run meeting
• technique inspection/walkthrough
system analyst and a programmer
• system analysis one who analysis system (study that problems and determine system user needs) identify solution that have occasion
• a programming one who write program codes into computer system. where is code at write by virtue of analysis from a system analysis.
mention what are the knowledge a system analyst should posses
• knowledge and skill about technique processing data
• knowledge about business in general
• knowledge about quantitative method
• trouble-shooting skill
• skill in communicate with staff
• skill in build connection with staff
teken from :
* analisis & desain system
* slide Part 2 - PENGEMBANGAN SISTEM.ppt
• Because problems of the long system, the problem be appear is :
- crummy Settled of the long system because the long system can’t operate with good. Many fraudulent with expressly that result , it’s make money firm not safe.
- Not intentional the wrong can cause truth from data less
- Don’t the efficient data
- Don’t the loyal with firm
• Development organization
Between is information more and more extensive, data volume more increase, principle change new accountancy. Because it change, then the long system not effective again.
• For reaches to chances
Because with development system information, organization can take decision swiftly and make sever by quick.
• existence Instructions (directives) from leadership, for example government regulation
Destination from information system development
• for make easy organization in break problem
• to make easy to get to chances existing
• to make easy to finish existing instructions
by applying information system, hope from a organization as following :
• performance
this measured from reduction and efficient time.
• information
this measured to make easy give information and easy information service.
• economy
with the new system information, hope organization is decrease cost for operation firm.
• Control
With the new system information, hope organization is make easy in detect and repair error from long system.
• Efficiency
Example : Decrease time for do a job in organization
• Services
It is destination fro increase from service system.
Principle from information system development
• System for management
Destination for make easy regulate organization from a firm
• System is big investment
Investigation all alternative(minimize opportunity cost the lost)
• System wants one who educated, not educate formal
• System development have to not massage, can done at random
• Don’t be afraid cancel project, it destination to avoid loss from a organization.
• System documentation, it destination to make easy to see from a system existing
System development life cycle
• life cycle model waterfall a method system the working gradually, in every stage can not return previous step. The step composition is requirements, design, implementation, verification, maintenance. With waterfall method, if step be verification we can’t previous to step design.
• life cycle with method itratif, by using this method our first does with initial planning, then requirement, analysis and design, then implementation, deployment, besides deployment we also do testing, then continued with evaluation. if there deficit or error in system, we can do new planning. this be difference between method waterfall with itratif. itratif can do change if there error in system.
• from life cycle spiral model, first step at does in spiral method concept of requirement that present in stage development, then concept of operation this present in stage plan, stage requirement plan that present in stage determine, risk analysis this present in stage identfy and resolve risk, get a temporary result then that is continued with stage venfication and validation, then development plan, risk analysis, produce a prototype 2, then at continue with venfication and validation, then at continue with test plan, continued again with risk analysis and produce oprational prototype, continued with detailed design, code, integration, test, implementation, and last is done release from system made.
approaches of developing a system
• will approach classic opponent will approach structured will approach this will emphasized that system development success when follow stage at system life cycle.
- pendekatan classic approach in system development that follow stages at system life cycle without supplied with tools and techniques memadai.
- pendekatan structured approach this that begun from beginning year 1970 called with approach structured. approach structured equiped with tools and techniques that wanted in system development so that end result from system that developed be got system so that end result from system the structure will be be defined well and clear.
• approach pieces opponent approaches system.
approach pieces be to approach system development that emphasized at one particular activity or certain application. approach system that pay attention information system as one integration unitary to each activity or the application.
• approach system comprehensive opponent approaches
approach sistem-menyeluruh be to approach menyang system together according to comprehensive. will approach this less synchronized for system complex because difficult to be developed. this be to approach classic approach modulate try broken complex system become some part or simple module, so that system easier will be understood and developed.
• approach opponent far jump approaches to bloom.
approach to jump -jauh apply change according to together use sophisticated technology. this change is many contains risk, because computer technology so fast bloom and to year coming be worn out. approach this too expensive, because need investment at the same moment. approach to bloom to apply sophisticated technology just for applications that need at that moment and then be developed for periods next will follow the need as according to existing technology development
meaning of methodology, method and algorithm
• methodology is unitary from methods, procedures, job concepts, rules that used by a science, art, or discipline the other
• method is a steps to in methodology
• algorithm is sequence procedure to break problem.
three classifications of development methodology
• functional decomposition methodologies
this methodology constitute in solution from system into sub system smaller. belong into group methodologies this:
- HIPO (hierarchy plus-process-output)
- Stepwise refinement (SR) or iterative stepwise refinement(ISR)
- Information-hiding
• Data oriented methodologies
- Data flow methodologies
this methodology is in general is based in solution from system intoes modules based on from type element data and module logic behaviour in system
- Data structure oriented methodologies
this methodology emphasizeds structure from input and output at system. mask in this methodology: jsd (jakson's systems development) and w/o(warnier/orr)
tools for developing a system
• system development tool:
HIPO diagram, used in metodelogi HIPO
Data flow diagram, used in system analysis and design S
Structured chart, used at method wanier/orr
Jakson's diagram, used at methodology jakson's system development
Techniques used in developing a system
techniques that can be used :
• technique management project, that is CPM(critical part method) and PERT (program evaluation and review technique). This technique used in project scheduling.
• Fact finding techniques, that is technique that can be used to gather fact and find data in activity study existing activity.
• technique analysis cost/benefit (cost-effectiveness analisys or cost-benefit analysis)
• technique to run meeting
• technique inspection/walkthrough
system analyst and a programmer
• system analysis one who analysis system (study that problems and determine system user needs) identify solution that have occasion
• a programming one who write program codes into computer system. where is code at write by virtue of analysis from a system analysis.
mention what are the knowledge a system analyst should posses
• knowledge and skill about technique processing data
• knowledge about business in general
• knowledge about quantitative method
• trouble-shooting skill
• skill in communicate with staff
• skill in build connection with staff
teken from :
* analisis & desain system
* slide Part 2 - PENGEMBANGAN SISTEM.ppt
Langganan:
Postingan (Atom)
