Last night my father came to me bring me an clipping from his favorite newspaper. After i look at the clipping and read on flash, I know that the clipping tell about Erasmus Mundus Scholarship offers scholarship for students from third country like Indonesia. I think this is a great chance to became an abroad student in Europe. I notes the url link an would take a look tommorow.

Today  I have take look some courses which is offered by Erasmus Mundus. There are some program be related with my field , computer science . One of them is NORDSECMOB – Masters programme in Security and Mobile Computing and MAPNET – Masters on Photonic Networks engineering .

For the firs time i attracted with course that offered by NORDSECMOB but the admission deadline is December 1 2009 and i am not ready especially with the English certificate ex TOEFL or IELTS. The minimum requirement is 550 for TOEFL or 6.5 for IELTS. My TOEFL score just for 507 and I still join a TOEFL Preparation Course to gain a higher TOEFL score. MAPNET deadline is January, 10 2010 . I think i still have a chance for MAPNET.  I know that is a great challenge to get 550 TOEFL fora m0nth.  Yeah life must go on and everyone must struggle to reach their dream. Jiayou

What dou you think about paid reviewer? May be if you ask that question 1 day ago to me, i can’t ansewr that question. But now i already know about what is a paid reviewer, thank a lot to my lecturer that have explain to me what is a paid reviewer. Of course he can explain to me about paid reviewer becaouse he is have beem long time became a paid reviewer so we can called him a senior paid reviewer.

The first thing that attacted me to became a paid reviewer is the easy way to get money. He have told to me about 200$ income /month. What a big money! i think. Just after he explain a short step to me to became a paid reviewer , i get to try it.  The first thing that you should have to became a paid reviewer is a blog. Your blog have alive in the internet for 3 month and then you should sign up an account to some broker for example is blovertise or blogvertiser whom would give you a job.

I add 1-N cardinality in relationships and PROJECT and BAGIAN because:
- 1 BAGIAN can handle a lot of PROJECT and,
- Many PROJECT  can be handled by 1 BAGIAN

Therefore, it is then there are rules that I use during the mapping. Rules are:
1. If the relation 1-N in the primary key (1) move to (N) and vice versa applies.
2. If the relationship M-N will be created a new table with the primary key of each entity will be became the primary  key in the new table.
3. If the relationship 1-1 then choose  higher  cardinality to put primary key for a foreign key in relation table .
4. If the dependent relationships of the primary key table dependent primay key derived from the mother entity.

So from that rules, i struggle to mapping that ERD, here isi the tables :

Fro that mapping above, we can see that tables created from mapping have meet 3NF normalization.  Because the relation should not have a nonkey attribute functionally determined by another nonkey attribute ( or by a set of nonkey attributes). That is, there should be no transitive dependency of a non key primary key.

DATABASE NORMALIZATION

Database design process (review):
- Gather user needs / business
- Develop a needs-based ER Model user / business
- Convert E-R model to the set of relations –> tables in database
- Normalisasikan relations, to remove anomalies
- Implemented to create a database with a table for each relationship that is  normalization

Database normalization
- Normalization process is the establishment of the database structure so that most of the ambiguity can be removed.
- Normalization stage, starting from the most mild (1NF) to most stringent (5NF)
- Usually only up to the level of 3NF or BCNF because already sufficient to generate the good quality table.

Why do normalization?
- Optimizing table structures
- Increase speed
- The income data is the same
- More efficient in the use of storage media
- Reduce redundancy
- Avoid anomalies (insertion anomalies, deletion anomalies, update anomalies).
- Improved data integrity

A table can be effient/good table if the table meet the 3 following criteria:
- If there is decomposition  table, it must be guaranteed have safe decomposition (Lossless-Join Decomposition). That is, after the table is described a new table-table, the table-table can generate a new table with the same exact.
- Maintain dependence on the functional changes in data (Dependency preservation).
- Does not violate Boyce-Code Normal Form (BCNF)
If the three criteria (BCNF) can not be met, then at least the table does not violate the Normal Form of the third stage (3rd Normal Form / 3NF).

Functional Dependency
Functional Dependency describes a relationship attributes in relation
An attribute said functionally dependant on the other, if we use the value attribute to determine the value of the other attributes.
Symbol that is used (->) to represent the functional dependency.

Notation: A -> B
A and B are attributes of a table. A means of determining the functional B or B depends on A,
if and only if there are 2 rows of data with the same value of A, then B is also the same value
Notation: A -> B or A x-> B
It is the opposite of the previous notation.

Functional Dependency:
NRP -> Name
Mata_Kuliah, NRP -> Value
Non Functional Dependency:
Mata_Kuliah -> NRP
NRP -> Value

Functional Dependency of the table value
Nrp -> Name
Because for each value Nrp the same, then the value of the same name
(Mata_kuliah, NRP) -> Value
Because the value of attributes depending on the NRP and Mata_kuliah together.
In another sense Mata_kuliah for the NRP and the same, they also rated the same,
because Mata_kuliah and the NRP is a key (is unique).
Mata_kuliah -> NRP
NRP -> Value

FIRST NORMAL FORM 1NF
A table on the form said to be normal if I did not reside in the unnormalized form of a table, where there is a kind of field multiplication and field that allows a null (empty)
Not allowed:
Many attributes of value (Multivalued attributes).
Attributes composite or a combination of both.
So: Price is the domain attribute must be atomic rates

The table above does not meet the requirements 1NF

Decomposition as follows :

SECOND NORMAL FORM – 2NF
Normal form 2NF met in a table if it meets the form of 1NF, and all the attributes than the primary key, have a full
Functional Dependency on primary key
A table does not meet 2NF, if there are attributes that dependency (Functional Dependency) are only partial (only depending on the part of the primary key)
If there are attributes that have no dependence on the primary key, then the attributes must be moved or removed

Functional dependency X -> Y is full if it is said to delete an attribute A from X means that Y is no longer dependent functional.
Functional dependency X -> Y said if deleting a partial attribute A from X means that Y is functionally dependent.
Relation scheme R in the form 2NF if every non-primary key attribute A e R depend on the full primary key fungsioanl R.

Does not meet 2NF, because (NIM, KodeMk) is regarded as the primary key:
(NIM, KodeMk) -> NamaMhs
(NIM, KodeMk) -> Address
(NIM, KodeMk) -> Matakuliah
(NIM, KodeMk) -> SKS
(NIM, KodeMk) -> NilaiHuruf
Table needs to be some table decomposition eligible 2NF

Functional dependency as follows:
(NIM, KodeMk) -> NilaiHuruf (fd1)
NIM -> (NamaMhs, Address) (fd2)
KodeMk -> (Matakuliah, SKS) (fd3)
So that:
fd1 (NIM, KodeMk, NilaiHuruf) -> Value Table
fd2 (NIM, NamaMhs, Address) -> Table Student
fd3 (KodeMk, Matakuliah, SKS) -> Table MataKuliah

THIRD NORMAL FORM – 3NF
Normal form 3NF fulfilled if the form meets 2NF, and if there are no non-primary key attribute
that has a dependence on non-primary key attributes of the other (transitive dependencies).

The following table meet 2NF, but not meet 3NF :

Because there are non-primary key attribute (ie, City and Provincial), which has a dependence on non-primary key attributes of the other (ie KodePos):
KodePos -> (City, Province)

So that the table should be dicomposition as follows:
Student (NIM, NamaMhs, Road, KodePos)
KodePos (KodePos, Province, City)

Boyce-Codd Normal Form (BNCF)
Boyce-Codd Normal Form constraint has a stronger form of the Normal third.
To be BNCF, relations must be in the form of 1NF and forced each of the attributes depends on the function in the super key attributes.
In the example below there is a relationship seminar, is the Primary Key NPM + Seminar.
Students may take one or two seminars. Each seminar requires 2 each of the students and led by one of the 2 seminar.
Each leader can only take one seminar course. NPM and Seminar in this example show a Pembimbing.

4 NORMAL FORM and 5 NORMAL FORM
Relations in the fourth normal form (NF 4) if the relation in BCNF and dependency not contain many values.
To remove the dependency of many values from a relation, we divide the relationship into two new relations.
Each relation contains two attributes that have a lot of relationship value.
Relations in fifth normal form (5NF) deal with the property called the join without any loss of information (lossless join).
Fifth normal form (also called the 5 NF PJNF (projection join normal form).
The case is very rare and appear difficult to detect in practice.

Definition of the database:

A set of data stored in the magnetic disk, optical disk or other secondary storage

Collection of integrated data-related data of an enterprise (company, government or private)

Manufacturing companies -> data production planning, actual production data, data ordering materials, etc.

Hospital -> patient data, doctor, nurse, etc.

Database Management System

- Collection / database combined with software applications that are based database

- Application programs are used to access and maintain databases

- The main purpose DBMS is to provide an environment that is efficient and easy to use, withdrawal and storage of data and information

Size in Database

Bit -> data is the smallest that contains the value 0 or 1

Bytes -> the set of bit-bit similar

Field -> byte-byte set of similar, in the database used the term attribute

Field / Attribute

It is the nature or characteristics of an entity that provides provide detail on these entities

A relationship can also have attributes

Example attributes:

STUDENTS: NIM, NAME, ADDRESS

CAR: NOMOR_PLAT, COLOR, TYPE, CC

Attribute Type :

- Single vs Multivalue

Single -> can only be filled at most one value

Multivalue -> can be filled with more than one value with the same type

- Atomic vs Composit

Atomic -> can not be divided into the attributes of smaller

Composition -> is a combination of several attributes of a smaller

- Derived attribute

attribute value can be derived from other attribute values, eg, -> age resulting from the date of birth attribute

- Null Value attribute

Attributes that have no value to a record

- Mandatory attribute Value

Attributes must have values

Record / Tuple

It is a line of data in a relationship

Consists of the set of attributes where the attribute-attribute-attribute is to inform each

other entity / relationship fully

Entity / File

File is a collection of similar records and have the same elements, the same attributes but different data value.

File Type

In processing applications, files can categorized as follows:

- Master File

- Transaction File

- File Report

- File History

- File Protection

- Job File

Domain

Domain is the set of values that are allowed to reside in one or more attributes.

Each attribute in a relational database is defined as a domain

Key Element

Key elements of record which is used to find these records at the time of access,

or can also be used to identify each entity / record / line.

Key Type :

- Superkey

is one or more attributes of a table that can be used to identify entity / record

of the table are unique (not all attributes can be superkey)

- Candidate Key

is a super key with minimal attributes. Candidate must not contain a key attribute

of the table so that the other candidate key is certain superkey but not necessarily vice versa.

- Primary Key

One of the key attributes of the candidate can be selected / specified a primary key with

the three following criteria:

1. Key is more natural to use as reference

2. Key is more simple

3. Key is guaranteed unique

- Alternate Key

is an attribute of the candidate key is not selected to be primary key.

- Foreign Key

is any attribute that points to the primary key in another table. Foreign key will be going on a relationship that has cardinality one to many (one to many) or many to many (many to many). Foreign key is usually always put on the table that point to many.

- External Key

is a lexical attribute (or set of lexical attributes) that values are always identify an object instance.

Entity Relationship Diagram (ERD)

ERD is a model of a network that uses word order is stored in the abstract system.

Differences between the DFD and ERD

DFD is a model of network functions that will be implemented by the system

ERD is a model that emphasizes the network data on the structure and relationship data

ERD’s Elements :

- Entity

In the ER Diagram Entity is described with the form of a rectangle. Rntity is something that exists in the real system and the abstract where the data stored or where there are data.

- Relationship

ER diagram on the relationship can be described with a lozenge. Relationship is a natural relationship that occurs between entities. In general, the name given to the verb base making it easier to do the reading their relationship.

- Relationship Degree

is the number of entities participating in a relationship. Degree which is often used in the ERD.

- Attribute

is the nature or characteristics of each entity and relationship

- Cardinality

tuple indicates the maximum number that can be related with entities on the other entity

Relationship Degree :

- Unary Relationship

model is the relationship between the entity originating from the same entity set.

- Binary Relationship

model is the relationship between 2 entities.

- Ternary Relationship

is a relationship between the instance of 3 types of entities are unilateral.

There are 3 cardinality relations, namely :

- One to One: Level one to one relationship with the one stated in the entity’s first event, only had one relationship with one incident in which the two entities and vice versa.

- One to Many or Many to One: Level one to many relationship is the same as the one to many depending on the direction from which the relationship .For an incident on the first entity can have any relationship with many incident on the second entity, if the one incident on the entity the second can only have one relationship with the incident on the first entity.

- Many To Many: if any incident occurs in an entity many have relationships with other entities in the incident.

Data Flow Diagram Also called DFD

DFD goal :

- Describes the distribution of the modules to a smaller point of view

- Easier for users with less understanding to understand the field of computer systems that will be done

DFD consist of 3 diagrams , there are :

1. Context Diagram
2. Zero Diagram
3. Detailed Diagram

Context Diagram

1. DFD consists of a process and describe the scope of a system
2. Is the highest level of the DFD that describes the entire system to the input of the system and the output
3. System is limited by system’s boundary
4. No storage

Zero Diagram

1. Describes the process of the DFD
2. Providing views on the overall system in which, showing the main function or process that is, the flow of data and entity eskternal
3. At this level of data storage possible
4. To process that does not dirinci again on the next level then added to the symbol ‘*’ or ‘P’ at the end of the process
5. Balance of input and output (balancing) between 0 to diagram context diagram should be maintained

Detailed Diagram

Is a diagram that decipher what is the process in the diagram zero level or above

Numbering level in the DFD:

In one level there should be no more than 7 units and the maximum of 9, when more should be done in the decomposition

Process Specification :

1. Each process in the DFD must have a specification process
2. At the top level method is used to describe the process can use a sentence with descriptive
3. At a more detailed level, namely on the bottom (functional primitive) requires specification of a more structured
4. Specification process will be the guideline for the programmer to make this program (coding)
5. Method used in the specification process: the process of disintegration in the form of a story, decision table, decision tree

External Input

1. Something that is outside the system, but it provides data in the system or to provide data from the system
2. Symbol by notation
3. External entity not part of the system including
4. Naming:
   • The name of the form of noun
   • Terminal may not have the same name except the same objects

Flow of Data

1. Place for flow of information
2. Depicted with the straight line that connects the components of the system
3. Data flow direction is indicated with arrows and lines give the name on the flow of data that flows
4. Flow data flow between processes, data storage and data flow indicates that the form of data input for the system

Guidelines of the name:

1. Name of the flow of data that consists of some words associated with the flow lines connect
2. No flow data for the same and the name should reflect its content
3. The flow of data that consists of several elements can be expressed with the group element
4. Avoid using the word ‘data’ and ‘information’ to give a name to the flow of data
5. Wherever possible the complete flow of data is written

Other provisions:

1. Name of the flow of data into a process may not be the same as the name of the data flow out of the process
2. Data flow into or out of data storage does not need to be given a name if:
   • The flow of data simple and easy to understand
   • Describes the data flow of all data items
3. There can be no flow of data from the terminal to the data storage, or vice versa because the terminal is not part of the system, the relationship with the terminal data storage must be through a process

Process

1. The process is what is done by the system
2. The process can process data flows or data entry into the flow of data out
3. Transform the process of working one or more of the input data into one or more of the output data in accordance with the desired specifications
4. Each process has one or more inputs and produce one or more output
5. The process also often called bubble

Guidelines of the process:

1. Name of the process consists of a verb and noun, which reflects the function of the process
2. Do not use the process as part of the name of a bubble
3. May not have some process that has the same name
4. The process should be given a number. Order number wherever possible to follow the flow of the process or sequence, but the sequence number does not mean that the absolute is a process in chronological order

Data storage

1. Data storage is a storage place for data that exists in the system
2. Disimbolkan with a pair of parallel lines or two lines with one side open side
3. The process can retrieve data from or provide data to the database
4. Guidelines of the name:
   • The name should reflect the data storage
   • When his name more than one word must be marked with the number

DFD  Symbol :

Data Library

• Work to help the system to interpret the application in detail and organize all elements of the data used in the system precisely so that the system analyst and have a basic understanding of the same input, output, storage and process
• At analysis, the data dictionary is used as a means of communication between the systems analyst with the
• At the system design, data dictionary is used to design input, reports and databases
• Flow data on the global DAD, further details can be seen in the data dictionary

Load the data dictionary as follows:

• Name of data flow: must note that readers who need further explanation about a flow of data can find it easily
• Alias: alias or other name of the data can be written when there is
• Forms of data: used to segment the data dictionary to use when designing the system
• Flow data: indicates from which data flows and where the data
• Description: to give an explanation of the meaning of the data flow

Balancing In DFD

• The flow of data into and out of a process must be the same as the flow of data into and out of the details of the process on the level / levels below
• Name of the data flow into and out of the process must match the name of the flow of data into and out of the details of the process
• Number and the name of an entity outside the process must be equal to the number of names and entities outside of the details of the process
• The issues that must be considered in the DFD which have more than one level:
• There must be a balance between input and output of one level and next level
• Balance between level 0 and level 1 at the input / output of stream data to or from the terminal on level 0, while the balance between level 1 and level 2 is seen on the input / output of stream data to / from the process concerned
• Name of the flow of data, data storage and terminals at each level must be the same if the same objects

Restrictions in DFD

• Flow data may not be from outside the entity directly to other outside entities without going through a process
• Flow data may not be from the savings directly to the data to outside entities without going through a process
• Flow data may not be saving the data directly from the savings and other data without going through a process
• Flow data from one process directly to the other without going through the process of saving data should / be avoided as much as possible

]]> http://arnolditya.wordpress.com/2009/04/04/week-4/feed/ 2 arnolditya dfd http://arnolditya.wordpress.com/2009/03/27/week-3/ http://arnolditya.wordpress.com/2009/03/27/week-3/#comments Fri, 27 Mar 2009 04:22:45 +0000 arnolditya http://arnolditya.wordpress.com/?p=60 ]]>

Initial Observation and Needs Analisys

Why we need Initial Observation and Need Analisys? There are some reasons :
1.Gap difference between the purpose of the system and actual system conditions

2. Reports detection problem is not really real , i.e :
- Too ideal destination
- Lack of resources and / or attitude
- Measurement system is less accurate
- System that is the purpose behind
- The difference between the system and the iddle system

Problem solving:
the ongoing investigation in system detail
Getting a consensus that the ideal system
Developed several alternative
Selecting the best alternative
Goal of System Invesgation –> investigation indicates the problem is actually happening

Several problems in investigations that often appear are:
- Time
- Cost
- Science
- Politics
- Intervention

Results of the investigation is a recommendation that includes among others the following:
- Not to take any action if there is not problem found
- Perform system maintenance this is can be take for small problems
- Improving the ability or the skills
- Consider modifications to the system total
- Putting the problem to occur in the development plan system is carried out immediately

Investigation Tactics
Why we need tactics?
- Find all issues
- Knowing the causes of the emergence of problems
- Determine the appropriate solution
Investigation Tactics must be done so that all elements of the system can receive a quote a solution without disrupting their activities

There are some of the investigation tactics that can be done:
- Listen to opinions of the system
- Do not give the early breakthrough
- Compare the stories of some of the system against the same case
- Note the logical inconsistency problem

Investigation Technics
Direct :
- The questionnaire
- Frequently asked questions
- Observations
Indirect:
- Flow of procedure
- Reviewing documents
- Sample
- Tabular

Description’s System that can be found are :
- Input
- Output
- File
- Data elements
- Transaction volume and document action
- Data flow diagram

Needs Analisys
Stage of intensive interaction between the systems analyst with the end user where the system shows
the development team expertise to get feedback and trust so that the user get a good participation.

4 PURPOSE THAT WANT achieved:
- Explain the complete system
- Information system that describes the ideal
- Bringing information system to the ideal conditions at this time with attention to resource constraints
- Providing encouragement to the confidence in the system development

Methods that can be used :
- FAQ
- Kuisioner
- Observation
- Procedure analysis
- Observation documents

Problems in Resource :
- Time
- Money
- Expertise
- Technology
- External factors
Needs document analysis :
Landing analysis: Relationships with end users, the observation process, problems in data collection
The user needs: The need actual, reporting requirements, training needs and the influence of the new system
System constraints: Explain the constraints of time and cost, expertise, technology, and external factors
Documents such as data collection instruments, statistical consensus, the logical flow of data and phisik, data elements in the initial data dictionary.

How do I approach the condition of the system at this time with the condition of the ideal system?
- Creating an alternative to solve the problem of information system
- Best alternative is applied wisely

Options Strategies that can be choose :
- Distributed versus centralized processing
- Changes in decision-making information from the centralized data   processing to the end user Decentralized responsibility center
- Integrated versus dispersed database
- System designer must consider the data are entered in the data base and into the File
- Surround System of Strategy Development
- About important environmental strategy in the case of company takeovers because the information system of other companies may vary with the company at this time.

Options Tactics
Selection is done before the operational design

Designing Operational Options
Options can be grouped into the design :
Input :
- Online Vs Off Line Data Entry
- Keyed Vs Machine Readable Data Entry
- Centralized Vs Decentralized Data Entry
Processing :
- Batch Vs Realtime record update
- Sequential Vs Direct Access to records
- Single Vs Multiple Users update of records
Output :
- Traditional Vs Turn Around Documents
- Structured Inquiry Vs based reports

Selecting the proper system :
Compare tactics: systems based on the comparison of costs and benefits relative; There are 3 ways a system said the system is superior to the other if:
- A cost is lower than B and both are the same benefits
- A cost is lower than B and A yield advantage of more than B
- A and B have the same but the cost advantage generated a lot more.
Some compare System methods :
- Break Even point Analyisis
- Payback Period
- Discounted payback period
- Internal Rate of Return

Cost categories :
- Hardware
- Software
- People
- Suppliers
- Teleccommunications
- Physical sites
Cost details :
Comparing the cost of information systems through the life of the system, analysts memproyeksi how
the cost changes for the future and there are 3 models cost information system, namely Linear,
and exponentially Step Function

* Cost information system can occur only once and can also occur on an  ongoing basis.
* Cost information system that occur only once the cost ontime and development costs
that occur during the development of the system.
* Cost information system that occur continuously among reccuring cost and operational cost where the cost of this is the case when the operating system information every day.

Qualitative factors that lead the performance information system :
- Reduce errors
- Reducing the time to fix errors
- Reduce the response time from the workstation alternative
- Accelerate the time of providing information
- Improve security systems
- Propagate update records on the source
- Increasing user satisfaction

CORPORATE STRATEGY FACTORS :
- Customer satisfaction
- Sales increased
- Consumer and vendor commitment
- Information marketing products

Presenting learning SYSTEM :
- Make short presentations
- Reduce the detail description techniques
- Mempretasikan clearly with visual aids
- If using a model using a tool such as a laptop so that more informative
- Emphasize the benefits of the proposed system with some alternative information that is appropriate conditions experienced by the company.

Make Go- or No-Go Decision
If the company decided to develop the information system, the department will do next, namely the System Design Process.
If then the System Development Life Cycle (SDLC) will be terminated.
Often the problem will be found with the system and the study and top management will usually ask for the re-employment system to study.
Model will describe some of the stages of the repeated and sometimes the information will make a decision before the repeat stage system of study.
With the alternative, the decision to repeat a previous stage SDLC or not called Go – No-Go Decision.

This is all about our classes in information and system design from week 3..continue from Week 1 post..

Before we start to build and develop an information system, we need to know the reasons need to be done so that the development of a system. Here are some reasons for the development of a system :

1. There is a problem that needs to be completed. This is often experienced by many organizations. For example in a telecommunications company will require a great system for dealing with information communication notes clients. The problem would be very difficult if not using the information system

2. Irregularity in the growth of the organization. This is also experienced by many organizations. For example, an organization implement a system akutansi. Of course this requires information systems to handle the changes.

3. To reach opportunities. In the organization is often required information is obtained only with implementing information systems in organizations. This valuable information that can later be used to gain opportunities in the organization.

4. Having the instructions. Sometimes the way the organization will meet the demands of the instructions the relevant authorities. For example of the new government set a minimum wage, the system required the development of existing information.

Of reasons, it can be the goal of the development system is as follows:
1. Solving problems.
2. Reach the opportunity
3. Intruction meet the given

Now let we discuss about is expected from developin system.
1. Performance
Measured using the throughput and response time
2. Information
Improving the quality of information
3. Economyc
Increasing the benefits vs. cost reduction
4. Control
Detect and fix errors
5. Efficiency
Efficient operations
6. Services
Improvement of the system

What are the principles of developing an information system?
There are seven priciples of developing an information system :
1. System for management
2. System is a large investment
- Investigate all alternatives (minimize cost of lost opportunity)
- Investigation must be best value: cost-benefit analysis & cost-effectivenes analysis
3. Systems require educated people
There must be formal education
4. Stages of labor -> System development life cycle
5. Development of the system does not need to order
6. Do not be afraid to cancel the project
7. Documentation system

System Development Live Cycle (SDLC)

Waterfall Method:

1. Requirement: At this stage we determine the needs of the system. Identify the problem, detect potential problems and to complete the goal of making system. This stage is very important because at this stage we menetukan way of making system.
2. Design: In this step, we created a design system based on the analysis of the needs we have done in the previous stage.
3. Implementation: At this stage, we try to implement the system we have pata design stage before.
4. Verification: At this stage we do verification of the system we have implemented. If all are not running and there is a design error in the system that we implemented.
5. Maintenance: This stage will continue to be used throughout the system. Because at this stage is done so that treatment can continue to run the system in accordance with the expected

Iteratif Method:

Model here is almost the same as the waterfall model, only after the system been use, there will be trials of the system. Evaluation of testing done to know the weaknesses in the system, if there is an error, then the system will reset in the analysis.

Spiral Method:

This method is almost the same as the method iteratif, only in this method continues to be improvements for the development system. This is done by creating a prototype-prototype before the final version are released.

Ok , now after discuss System Development Live Cycle ..there are five approach of developing a system :
1. The classical approach vs structured approach
- Classical approach
Stages in the SDLC
Did not include users, system analysts put more emphasis
Problems: the development of hard, expensive treatment, the possibility of error, success is less assured, the        problems in the implementation of

- Structured approach
Users involved from the beginning to determine the needs of the system
Using tools-tools such as data flow diagrams

2. The piece approaches vs the system approach
- The piece approach
Emphasizing on an application or event
Does not override the overall target

- System Approach
View the system as a whole is unity
Emphasis on achieving the overall target

3. Bottom-Up approach vs. top-down approach
- Bottom-Up approach (bottom-up)
Starting from the bottom level of the operational
Is a discrete approach to classical
Known by the term data-analysis

- Top-down approach (top-down)
Starting from the top-level strategy planning
Is a discrete approach to structured
Also known with the decision-analysis

4. The system-comprehensive approach vs. modular approach
- Comprehensive approach
Develop a system simultaneously and comprehensively
Is a discrete approach to classical

- Modular approach
Split the system into the complex parts of a simple
System to be developed on time, easy to understand and kept
Is a discrete approach to structured

5.The great-loop approach approach vs. evolutionary approach
- Great-loop approach
Develop a system simultaneously using the advanced technology
High-risk and spend a lot of cost
- evolutionary approach
Applying advanced technology for application-specific applications
Developed for the needs
Cost effective and can follow the development of technology

That’s so important to us to understand about step for develop a system. There are some points to note :
What is the methodology?
Methodology are methods used in science
What is the method?
Method is a systematic way to grind
What is the algorithm?
Algorithm are sequence procedures to solve a problem

Three classifications of development methodology :
1. Functional decomposition
- Emphasize breaking system subsystem
- Example: HIPO, Stepwise refinement, iterative stepwise refinement, information hiding

2. Data-oriented
- Emphasizes the characteristics of the data processed
- Data-flow oriented: modules according to the type of data elements
- Data-oriented structure: the structure of input and output

3. Prescriptive
Usually provided by the manufacturer of the software

Tools for developing a system :
1. Shaped graph: HIPO, SADT, Jackson’s diagram, and other

Tools that use the chart:
- Charting activity: describes the activities, for example: Gant chart, flowchart, etc.
- Layout charting: describes the layout
- Charting a personal relationship: describes the relationship of personnel, for example: organization charts, work  distribution chart

Techniques used in developing a system :
- Techniques for project management -> scheduling project, for example: CPM and pert
- Techniques to gather facts and determine the data / facts
* Interview
* Observation
- Technical analysis of cost / benefit -> cost-benefit and cost-Effectiveness analysis
- Techniques to run a meeting
- Technical inspection

The differences of being a system analyst and a programmer :
- Analyst system: study of the problems and determine the needs of the system to identify solutions
- Programmers: write a program code based on the building design is created by the analyst
System analyst duty bridge the knowledge gap that occurs between the user and system programmers

The knowledge a system analyst should posses :
- Technology, data processing, computer programming and business knowledge in general
- Quantitative methods: regression, linier programming, dsbnya
- Problem-solving skills
- Communication skills among the personnel
- Expertise builds relationships between the personnel

Wuihh..gila rek..hampir 2 tahun gak nulis blog..untung sik aktif ni blog..:D

Sik..sik sekarang ini mesti pake bahasa inggris ngblognya..:D

Oke..oke jadi kita akan mulai pake bahasa inggris.., Jadi saat ini kita akan membahas tentang ADSI…”eit..eit mas..kok pake bahasa indonesia?”…hehehe

Ok…now start writing in english..:D

Let us start about ADSI..!
Do you know what is ADSI?..wekekeke..That is funny acronym if we remove the “D”..:D
Yes..right..ADSI is acronym from Analisis dan Desain Sistem Informasi..one of more course that I was take..

Ok let we discuss about what is System and Information.

Why we must discuss that first?
Yeah..from information that i was get from my lecturer..before we discuss how to design information system..first we must
understand what is System and Information..

Ok first..What is System?

from Jogiyanto,Analisis dan Desain Sistem Informasi that is 2 approachment to define what is System..

1. From procedure Approach
System is network from procedure-procedure where they are connected and working together to reach the same goal.

Now..what is procedure?..:D
from the same books..procedure is described as :
treads from step-step instruction that’s describe What is must to do ,Who is do that , when that is must to do and how they must to do.

2. From elemen Approach
System is elemen-elemen that is gathered and work together to reach the same goal.

And the one is important to see is :
sasaran(objective) is jangka pendek
tujuan (goal) is jangka panjang

And after we know about definition from system..there is many characteristics from System.

The characteristics is:

1. component
2. boundary
3. environments
4. interface
5. input
6. output
7. process
8. objective/goal

The most important item from characteristics of system is objective/goal. A System must have objective or goal . If they have no goal/objective to reach..there is useless we build that system.

There i am have a picture to show how relationship from characteristics in system

Maybe i can explain some example from component’s of system,,

The environments of system

The environments of system can take some effects to system. They can have a good effect or bad effect.

for example : In a town with some of supermarkets. If one of them have sold some item with a more cheap price from the other supermarkets..there is an bad environment for supermarkets in  that town.

There are many example to illustrate characteristics from system..,, Do you have some other example??..:D

And then after characteristics , let us discuss about classification of system. From Jogiyanto,Analisis dan Desain Sistem Informasi , there are four classification of system..there is :

1. Abstract System and Physical System

Abstract system is system which in the form of ideas. Example teologia system, system which in the form ideas about relation between human with God.

Physical System is existing system physically. For example, computer system, accounting system, etc.

2. Natural System and Human made System

Natural system is system that happened through by natural process, do not be made human being. For example earth rotation, eclipse, etc.

Human made system is design system by human being. Interaction between human with machine to make a system is called man-machine-system. For Example information system.

3. Deterministic System and Probabilistic System

A deterministic system is a conceptual model of the philosophical doctrine of determinism applied to a system for understanding everything that has and will occur in the system, based on the physical outcomes of causality.

A probabilistic syetem is a system which condition of its future can’t prediction because containing probability element.

4. Closed System and Open System

In reality there no really closed system, existing is relatively closed system. Open system is relation between system and affect system of its external environment.

Ok…enough for system..:D

Information

What do you think about information??

Yes..i have some opinion with you..hehehe

Information is some data which have been processed to make they more usefull for who will receive the data.

Has you have different opinion with me?..

There is a cycle to process some data into information..for more easy to understand..i have a picture to illustrate the cycle..

To explain the picture i  have some illustrate for you..

For example Supermarket A have an information system ..ok may be POS (point of sale) more familiar  .

• the first step the manager will reach some information from the POS data. Ok..let we assume sale of banana is good for 3 last month.
• from that information the manager can take some decision..there is the supermarket will provide more kinds of banana.
• from that decision..the manager can look the effect from POS’s data of this month sale of banana.
• And from the new data which will be processed to information the manager can take some decision to  improve next month sale.

To classify the information , we can look from the quality of information . There are some parameter to assesing information. The parameters is :

- Accurate

Accurate means information have to free from mistakes and do not mislead

– Timeliness

Timeless means incoming information may not lose time.

– Relevance

Relevance means the information must have benefit for its receiver.

this is the logic to get information :

A information told valuable, if its benefit more effective compared to expense to get it. Its will very is difficult measured by set of money value. Measurement value of information is usually attributed to analysis of cost effectiveness or cost benefit.

Ok enough for Week 1..see you later at Week2…:D

Tiga negara, yaitu Amerika, Inggris, dan Indonesia berlomba-lomba menentukan siapa diantara mereka yang lebih dulu menggunakan teknologi
canggih dengan meneliti keadaan tanah negaranya masing-masing untuk melihat siapa yang terhebat di masa yang lalu.
Disepakati penelitian dimulai dari Amerika trus Inggris & terakhir Indonesia.
Di Amerika, stl penggalian sudah mencapai 1000 meter maka ditemukan kabel tembaga, maka Team Amerika dengan banggannya menyimpulkan
bahwa 1500 tahun yang lalu telah dibangun jalur telepon dengan memakai tembaga di Amerika.
Di Inggris, setelah penggalian sudah mencapai kedalaman 1000 m tidak ditemukan kabel tembaga, tetapi setelah mencapai kedalaman 1500 m ditemukan serpihan kaca maka Team Inggris tersebut dengan bangganya menyimpulkan bahwa 2500 tahun yang lalu telah dibangun jalur komunikasi dengan memakai Fiber Optik di Inggris
Dan terakhir di Indonesia, setelah penggalian sudah mencapai kedalaman 500 m dan 1000 m sampai seterusnya tidak ditemukan apa-apa, lalu dgn sangat bangganya, maka Team Indonesia menyimpulkan bahwa 5000 tahun yang lalu komunikasi di sini telah menggunakan wireles.