Thursday, October 3, 2013
What is Traditional Cryptography?
Posted by
Sunflower
at
10/03/2013 08:15:00 PM
0
comments
Labels: Algorithms, Application, Authentication, Cryptography, Data, Encrypt, Encryption, Information, Message, Modern, Protection, Protocols, Secure, Security, System, Techniques, traditional
![]() | Subscribe by Email |
|
Friday, December 28, 2012
What is the difference between Purify and traditional debuggers?
- Bug
finding capabilities from the rational purify,
- Performance
tuning effects from the rational quantify and
- Testing
rigors from the rational pure coverage.
About IBM Rational Purify
Difference between Rational Purify and Traditional Debuggers
- Array
bounds
- Access
to un-allocated memory
- Freeing
the memory that is un-allocated
- Memory
leaks and so on.
Posted by
Sunflower
at
12/28/2012 12:23:00 PM
0
comments
Labels: Application, Benefits, Code, Debugger, Dynamic, Errors, Functionality, IBM rational, IBM Rational Purify, Languages, Memory, Performance, program, Programs, Quality, Reliability, Static, Testing, Tools, traditional
![]() | Subscribe by Email |
|
Friday, July 27, 2012
What are the causes for the failure of traditional planning approach?
Causes for Planning Failure
Cause #1: Planning is done by activity and not feature
- The traditional approaches to planning focus on activity completion rather than on delivery of features.
- Activity based plans generally lead to projects that overrun their schedules.
- Hence, quality is reduced.
Cause #2: Activities do not finish early
Cause #3: Lateness is passed down the schedule
- Traditional approaches being activity based, their main focus is to focus on dependencies between activities.
- Testing will start late if anything goes worse than planned according to traditional approach.
- Testing will start early if everything goes better than planned.
Ways to avoid late start of testing are:
1. User interface coding finishes late.
2. Middle tier coding takes longer than planned and finishes late.
3. Middle tier coding starts late as tables adding to database finishes late.
4. Tester is not available.
Cause #4: Activities are not independent
- Activities are independent if duration of one activity does not influence the duration of another activity.
- For independent activities, late finish on one activity can be offset by an early finish on another.
Cause #5: Delay caused by multitasking
- Multitasking exacts a horrible toll on productivity.
- It becomes an issue once a project starts to have some activities that finish late.
- Dependencies between activities become critical.
- For a traditionally planned project, multitasking becomes a problem for two reasons:
1. Work is assigned in advance and it is impossible to allocate work efficiently in advance.
2. It focuses on achieving high level of utilization of all individuals rather than on maintaining sufficient slack.
Cause #6: Features are not developed by priority
Cause #7: Ignoring Uncertainty
- We fail to acknowledge uncertainty in traditional approach.
- Ignore the uncertainty about product.
- Assuming initial requirement analysis will lead to complete specification of product.
- Ignoring uncertainty about how we will build the product.
- The best way to deal with uncertainty is to iterate.
After looking at the problems with traditional approaches to planning, many projects are disappointing. Planning based on activity diverts us from features and as a result, a variety of problems leads to the likelihood of delivering late against a schedule.
Posted by
Sunflower
at
7/27/2012 10:16:00 PM
0
comments
Labels: activities, Activity, Activity based plan, Approach, Dependency, Duration, Features, Focus, Independent, Multitasking, Plan, Planning, Projects, Reasons, Results, Schedule, Testing, Time, traditional, User Interface
![]() | Subscribe by Email |
|
Monday, August 3, 2009
Introduction to Databases
Databases play an important role in almost all areas where they are used including business, engineering, medicine, law, education, and library science, to name a few.
A database is a collection of related data, where data means recorded facts. A typical database represents some aspect of the real world and is used for specific purposes by one or more groups of users. Databases are not specific to computers. Examples of non-computerized databases abound: phone book, dictionaries, almanacs, etc. A database has the following implicit properties :
1. A database represents some aspect of the real world.
2. A database is a logically coherent collection of data with some inherent meaning.
3. A databse is designed, built, and populated with data for a specific purpose.
4. A databse can be of any size and of varying complexity.
5. A database may be generated and maintained manually or it may be computerized.
A database management system (DBMS) is a collection of programs that enables users to create and maintain a database. The DBMS is a general-purpose software system that facilitates the process of defining, construction, and manipulating databases for different applications.
Defining a database involves specifying the data types, structures, and constraints for the data to be stored in the database.
Constructing a database is the process of storing the data itself on some storage medium that is controlled by the DBMS.
Manipulating a database includes such functions as querying the database to retrieve specific data, updating the database and generating the reports from the data.
CHARACTERSTICS THAT DISTINGUISH DATABASE APPROACH FROM TRADITIONAL FILE-PROCESSING APPLICATIONS :
- Existence of a catalog : It contains information such as structure of each file, the type and storage format of each data item and various constraints on the data. The information stored in catalog is called meta-data.
- Program data independence : In traditional file processing, the structure of a file is embedded in the access programs, so any changes to the structure of a file may require changing all programs that access this file. By contrast, the structure of data files is stored in DBMS catalog separately from access programs. This property is called program data independence.
- Program operation independence: Users can define operations on data as part of database applications. An operation is specified in two parts - interface of operation : includes operation name and data types of its arguments, implementation of operation : specified separately and can be changed without affecting the interface. This is called
program operation independence.
- Data abstraction : The characteristic that allows program data independence and program operation independence is called data abstraction.
- Support of multiple user views.
- Sharing of data among multiple transactions.
Main Categories of Database users are :
- Administrators.
- Designers.
- End users.
- System analysts and application programmers.
- DBMS system designers and implementers.
- Tool Developers.
- Operators and maintenance personnel.
Advantages of using Databases :
- Potential for enforcing standards.
- Reduced application development time.
- Flexibility.
- Availability of up-to-date information to all users.
- Economies of sale.
Posted by
Sunflower
at
8/03/2009 09:32:00 AM
0
comments
Labels: Advantages, Data, Databases, File processing systems, introduction, Properties, traditional
![]() | Subscribe by Email |
|