Firmoo

Firmoo
Firmoo

Quran Guidance of the Day

Thursday, February 23, 2012

Niat Shalat Sunat Jum'at dan Shalat Fardhu Jum'at

NIAT SHALAT SUNAT QOBLA JUMA'AT

Setelah adzan yang pertama selesai dikumandangkan, hendaklah dikerjakan shalat sunat 2 rakaat dengan niat:

USHALLII SUNNATAL JUMU'ATI RAK'ATAINI QABLIYYAN LILLAAHI TA'AALAA
artinya:
"aku niat shalat jum'at 2 rakaat sebelumnya, karena Allah ta'ala."

NIAT SHALAT FARDHU JUMA'AT

USHALLII FARDHAL JUMU'ATI RAK'ATAINI MUSTAQBILAL QIBLATI ADAA'AN MA'MUUMAN LILLAHI TA'AALAA
artinya:
"aku niat shalat fardhu jum'at 2 rakaat menghadap kiblat mengikuti imam karena Allah ta'ala."

jika menjadi IMAM maka kata MA'MUUMAN di ganti menjadi IMAAMAN.

NIAT SHALAT SUNAT BA'DA JUMA'AT

Jika shalat fardhu jum'at telah selesai dikerjakan, sebelum pulang hendaklah mengerjakan shalat sunat 2 rakaat, dengan niat:

USHALLI SUNNATAL JUMU'ATI RAK'ATAINI BA'DIYYATAN LILLAAHI TA'AALAA
artinya:
"aku niat shalat sunat jum'at 2 rakaat sesudahnya, karena Allah ta'ala."

WIRID DAN DO'A SETELAH SHALAT FARDHU JUM'AT

Apabila shalat fardhu jum'at telah selesai dikerjakan, Maka setelah salam hendaklah membaca:
a. Surat Al-Fatihah 7x
b. Surat Al-Ikhlas 7x
c. Surat Al-Falaq 7x
d. Surat An-Anaas 7x.

setelah itu membaca doa ini:
ALLAAHUMMA YAA GHANIYYU YAA HAMIID YAA MUBDI'U YAA MU'IID, YAA RAHIIMU YAA WADUUD, AGHNINII BIHALAALIKA 'AN HARAAMIK, WA BITHAA'ATIKA 'AN MA'SHIYATIK WA BIFADHLIKA'AMAN SIWAAK.
artinya:
"wahai Allah! Yang maha kaya, yang maha terpuji, yang maha mengadakan, yang maha mengembalikan, yang maha pengasih, yang maha mengasihi. Berikanlah aku kekayaan dengan barang-Mu yang halal, jauh dari barang yang haram, dan dengan berbuat taat kepada-Mu, jauh dari berbuat maksiat, dan dngan anugrah-Mu, jauh dari (meminta) kepada selain-Mu."
»» Readmore

Software Engineering (Rekayasa Perangkat Lunak)

Computer-aided software engineering
From Wikipedia, the free encyclopedia


Example of a CASE tool.
Computer-aided software engineering (CASE) is the scientific application of a set of tools and methods to a software system which is meant to result in high-quality, defect-free, and maintainable software products. It also refers to methods for the development of information systems together with automated tools that can be used in the software development process.

Contents
1 History
2 Supporting software
2.1 Tools
2.2 Workbenches
2.3 Environments
3 Applications
4 Risks and associated controls
5 See also
6 References
7 External links

History

The ISDOS project at the University of Michigan initiated a great deal of interest in the whole concept of using computer systems to help analysts in the very difficult process of analysing requirements and developing systems. Several papers by Daniel Teichroew fired a whole generation of enthusiasts with the potential of automated systems development. His PSL/PSA tool was a CASE tool although it predated the term. His insights into the power of meta-meta-models was inspiring, particularly to a former student, Dr. Hasan Sayani, currently Professor, Program Director at University of Maryland University College.
Another major thread emerged as a logical extension to the DBMS directory. By extending the range of meta-data held, the attributes of an application could be held within a dictionary and used at runtime. This "active dictionary" became the precursor to the more modern "model driven execution" (MDE) capability. However, the active dictionary did not provide a graphical representation of any of the meta-data. It was the linking of the concept of a dictionary holding analysts' meta-data, as derived from the use of an integrated set of techniques, together with the graphical representation of such data that gave rise to the earlier versions of I-CASE.
The term CASE was originally coined by software company Nastec Corporation of Southfield, Michigan in 1982 with their original integrated graphics and text editor GraphiText, which also was the first microcomputer-based system to use hyperlinks to cross-reference text strings in documents—an early forerunner of today's web page link. GraphiText's successor product, DesignAid, was the first microprocessor-based tool to logically and semantically evaluate software and system design diagrams and build a data dictionary.
Under the direction of Albert F. Case, Jr. vice president for product management and consulting, and Vaughn Frick, director of product management, the DesignAid product suite was expanded to support analysis of a wide range of structured analysis and design methodologies, notably Ed Yourdon and Tom DeMarco, Chris Gane & Trish Sarson, Ward-Mellor (real-time) SA/SD and Warnier-Orr (data driven).
The next entrant into the market was Excelerator from Index Technology in Cambridge, Mass. While DesignAid ran on Convergent Technologies and later Burroughs Ngen networked microcomputers, Index launched Excelerator on the IBM PC/AT platform. While, at the time of launch, and for several years, the IBM platform did not support networking or a centralized database as did the Convergent Technologies or Burroughs machines, the allure of IBM was strong, and Excelerator came to prominence. Hot on the heels of Excelerator were a rash of offerings from companies such as Knowledgeware (James Martin, Fran Tarkenton and Don Addington), Texas Instrument's IEF and Accenture's FOUNDATION toolset (METHOD/1, DESIGN/1, INSTALL/1, FCP).
CASE tools were at their peak in the early 1990s. At the time IBM had proposed AD/Cycle, which was an alliance of software vendors centered around IBM's Software repository using IBM DB2 in mainframe and OS/2:
The application development tools can be from several sources: from IBM, from vendors, and from the customers themselves. IBM has entered into relationships with Bachman Information Systems, Index Technology Corporation, and Knowledgeware, Inc. wherein selected products from these vendors will be marketed through an IBM complementary marketing program to provide offerings that will help to achieve complete life-cycle coverage.
With the decline of the mainframe, AD/Cycle and the Big CASE tools died off, opening the market for the mainstream CASE tools of today. Nearly all of the leaders of the CASE market of the early 1990s ended up being purchased by Computer Associates, including IEW, IEF, ADW, Cayenne, and Learmonth & Burchett Management Systems (LBMS).

Supporting software

Alfonso Fuggetta classified CASE into 3 categories:
Tools support only specific tasks in the software process.
Workbenches support only one or a few activities.
Environments support (a large part of) the software process.
Workbenches and environments are generally built as collections of tools. Tools can therefore be either stand alone products or components of workbenches and environments.

Tools
CASE tools are a class of software that automate many of the activities involved in various life cycle phases. For example, when establishing the functional requirements of a proposed application, prototyping tools can be used to develop graphic models of application screens to assist end users to visualize how an application will look after development. Subsequently, system designers can use automated design tools to transform the prototyped functional requirements into detailed design documents. Programmers can then use automated code generators to convert the design documents into code. Automated tools can be used collectively, as mentioned, or individually. For example, prototyping tools could be used to define application requirements that get passed to design technicians who convert the requirements into detailed designs in a traditional manner using flowcharts and narrative documents, without the assistance of automated design software.

Existing CASE tools can be classified along 4 different dimensions:
Life-cycle support
Integration dimension
Construction dimension
Knowledge-based CASE dimension

Let us take the meaning of these dimensions along with their examples one by one:
Life-Cycle Based CASE Tools
This dimension classifies CASE Tools on the basis of the activities they support in the information systems life cycle. They can be classified as Upper or Lower CASE tools.
Upper CASE Tools support strategic planning and construction of concept-level products and ignore the design aspect. They support traditional diagrammatic languages such as ER diagrams, Data flow diagram, Structure charts, Decision Trees, Decision tables, etc.
Lower CASE Tools concentrate on the back end activities of the software life cycle, such as physical design, debugging, construction, testing, component integration, maintenance, reengineering and reverse engineering.

Integration dimension
Three main CASE Integration dimensions have been proposed:
CASE Framework
ICASE Tools
Integrated Project Support Environment(IPSE)

Workbenches
Workbenches integrate several CASE tools into one application to support specific software-process activities. Hence they achieve:
a homogeneous and consistent interface (presentation integration).
easy invocation of tools and tool chains (control integration).

CASE workbenches can be further classified into following 8 classes:
Business planning and modeling
Analysis and design
User-interface development
Programming
Verification and validation
Maintenance and reverse engineering
Configuration management
Project management

Environments
An environment is a collection of CASE tools and workbenches that supports the software process. CASE environments are classified based on the focus/basis of integration

Toolkits
Language-centered
Integrated
Fourth generation
Process-centered
Toolkits
Toolkits are loosely integrated collections of products easily extended by aggregating different tools and workbenches. Typically, the support provided by a toolkit is limited to programming, configuration management and project management. And the toolkit itself is environments extended from basic sets of operating system tools, for example, the Unix Programmer's Work Bench and the VMS VAX Set. In addition, toolkits' loose integration requires user to activate tools by explicit invocation or simple control mechanisms. The resulting files are unstructured and could be in different format, therefore the access of file from different tools may require explicit file format conversion. However, since the only constraint for adding a new component is the formats of the files, toolkits can be easily and incrementally extended.

Language-centered
The environment itself is written in the programming language for which it was developed, thus enabling users to reuse, customize and extend the environment. Integration of code in different languages is a major issue for language-centered environments. Lack of process and data integration is also a problem. The strengths of these environments include good level of presentation and control integration. Interlisp, Smalltalk, Rational, and KEE are examples of language-centered environments.

Integrated
These environments achieve presentation integration by providing uniform, consistent, and coherent tool and workbench interfaces. Data integration is achieved through the repository concept: they have a specialized database managing all information produced and accessed in the environment. Examples of integrated environment are IBM AD/Cycle and DEC Cohesion.

Fourth-generation
Fourth-generation environments were the first integrated environments. They are sets of tools and workbenches supporting the development of a specific class of program: electronic data processing and business-oriented applications. In general, they include programming tools, simple configuration management tools, document handling facilities and, sometimes, a code generator to produce code in lower level languages. Informix 4GL, and Focus fall into this category.

Process-centered
Environments in this category focus on process integration with other integration dimensions as starting points. A process-centered environment operates by interpreting a process model created by specialized tools. They usually consist of tools handling two functions:
Process-model execution
Process-model production
Examples are East, Enterprise II, Process Wise, Process Weaver, and Arcadia.

Applications

All aspects of the software development life cycle can be supported by software tools, and so the use of tools from across the spectrum can, arguably, be described as CASE; from project management software through tools for business and functional analysis, system design, code storage, compilers, translation tools, test software, and so on.
However, tools that are concerned with analysis and design, and with using design information to create parts (or all) of the software product, are most frequently thought of as CASE tools. CASE applied, for instance, to a database software product, might normally involve:
Modeling business / real-world processes and data flow
Development of data models in the form of entity-relationship diagrams
Development of process and function descriptions
[edit]Risks and associated controls

Common CASE risks and associated controls include:
Inadequate standardization: Linking CASE tools from different vendors (design tool from Company X, programming tool from Company Y) may be difficult if the products do not use standardized code structures and data classifications. File formats can be converted, but usually not economically. Controls include using tools from the same vendor, or using tools based on standard protocols and insisting on demonstrated compatibility. Additionally, if organizations obtain tools for only a portion of the development process, they should consider acquiring them from a vendor that has a full line of products to ensure future compatibility if they add more tools.

Unrealistic expectations: Organizations often implement CASE technologies to reduce development costs. Implementing CASE strategies usually involves high start-up costs. Generally, management must be willing to accept a long-term payback period. Controls include requiring senior managers to define their purpose and strategies for implementing CASE technologies.

Slow implementation: Implementing CASE technologies can involve a significant change from traditional development environments. Typically, organizations should not use CASE tools the first time on critical projects or projects with short deadlines because of the lengthy training process. Additionally, organizations should consider using the tools on smaller, less complex projects and gradually implementing the tools to allow more training time.[5]
Weak repository controls: Failure to adequately control access to CASE repositories may result in security breaches or damage to the work documents, system designs, or code modules stored in the repository. Controls include protecting the repositories with appropriate access, version, and backup controls.

»» Readmore

Thursday, February 16, 2012

Are you a blogger? Add a link in your blog to exchange FirmOO FREE RX glasses or RX sunglasses


You can get a variety Eyeglasses for all you need at Firmoo.

Here are they link: www.firmoo.com

Please feel free to choose your eyeglasses at their online shopping.

Following is the link from another blogger address http://bloggerfreegifts.blogspot.com/2012/02/good-news-summer-gift-for-bloggers.html for your reference.

----------------------------------------------------------------------------------------

If you are a blogger, and we will send you a pair of sunglasses (both regular or prescription) or eyeglasses (also both plano or prescription) , we will pay all the expenses including the shipping.

As an exchange, we are sincerely asking for your favor to add a link of our website at the front page of your blog? If your blog is of independent domain, it will be highly preferred. For the anchor text and the name of website for the LINK, we will send to you after we receive your email.

If you need some kind of vision correction, i.e. you are near-sighted or far-sighted, please obtain your prescription from your eye doctor and then scan the copy to us. If you do not need any vision correction, then you can choose plano glasses or regular sunglasses.

Please you may choose your plano glasses or prescription eyeglasses at
http://www.firmoo.com/

And you can also choose your regular sunglasses or prescription (RX) sunglasses at :
http://www.firmoo.com/wrap-around-rx-sunglasses.html

Thanks ahead for spreading the mouth for us!

If you have further questions, please send me email at: liwenjie@yahoo.com

---------------------------------------------------------------------------------
»» Readmore

Monday, February 13, 2012

Tugas RPL Minggu 1

IF-1413 - Rekayasa Perangkat Lunak

13 February - 19 February

Deskripsi Tugas RPL Minggu 1

Pada minggu 1 ada 2 buah tugas yang harus dikerjakan dan dikumpulkan dalam waktu 1 minggu.

Deksripsi tugas

Tugas 1: Eksplorasi CASE (Computer Aided Software Engineering).

Tugas 1 dapat dikerjakan dalam dua sudut pandang berbeda (silahkan Anda memilih satu dari dua sudut pandang tersebut):

  • Eksplorasi beberapa CASE, membahas: jenis-jenis CASE, waktu pemakaian (pada tahap analisis, perancangan, pengujian, dsb), sifat (berbayar / free), kelebihan dan kekurangan setiap CASE, dsb.
  • Eksplorasi satu (1) CASE saja: Pilih satu buah CASE dan bahas: waktu pemakaian, cara pemakaian, cara install, fitur-fitur yang disedikan, kelebihan dan kekurangan CASE tersebut.

Tugas 2: Eksplorasi standar dokumentasi yang dikeluarkan organisasi IEEE, SEI, OMG, dan ISO. Eksplorasi berisi pembahasan: Kapan (pada tahap apakah) digunakan standar dokumentasi tsb, bagaimana cara penggunaan, versi terbaru, kekurangan dan kelebihan dll.

Format Laporan

Pengumpulan tugas dalam bentuk makalah. Karena ada 2 tugas, berarti ada 2 makalah. Setiap makalah terdiri dari 4 bagian besar:

  1. Latar belakang / pendahuluan
  2. Pembahasan
  3. Kesimpulan dan Saran
  4. Referensi ( buku, ebook, website acuan wajib dicantumkan )

Batas waktu pengumpulan

Tugas dikerjakan mulai sesi 3 dan dikumpul paling lambat tgl 22 Feb 2012.

Demikian disampaikan dan terima kasih,

Metahelgia

»» Readmore

Tuesday, January 17, 2012

How To Remove Services In Windows XP (remove service in mmc list)

Users can usually uninstall applications from their computers quite easily, however, for Windows services, of course you can disable a service, but the entry for it may still remain there.

In here we will see the steps for deleting a Windows service completely, rather than just disabling it.

Note: You should always delete services in safe mode, lest it causes you any problem, you may also want to create system restore points, just in case something goes wrong, check out a tool that will allow you to create system restore points with a single click.

Step 1: Open Service --> Start > Run and type in services.msc and hit the Enter key.

Step 2: In the Services applet, find the service that you want to delete permanently, right click it and click on the Properties from the menu.

Step 3: In the properties window, find the name of the service and copy it to your clipboard.
You may also want to stop the service, if it is running, this will kill all the running processes for it.

Step 4: Open command prompt, --> Start > Run and type in cmd the Enter key.
Once a command prompt has opened up, type the command sc delete service_name, replace service_name, with the name of the service you copied in step 3.

Once a service has been deleted you should see a message saying [SC] DeleteService SUCCESS, this should mean that the service has been deleted, to ensure that, just click on the refresh button in the services applet and confirm that the service has been deleted.

These are the only steps you require to delete services in Windows XP and Windows Vista, you do not require to install or download additional softwares to do it.
»» Readmore

Thursday, January 12, 2012

Castle Age

This is my favorite game on facebook.

Explore a land of Fantasy!

- Raise an army of Knights, Elves, Angels and other mythical creatures!
- Defeat Epic Monsters like Hydras and Dragons with Friends!
- Control Mighty Heroes to lead your army into battle!
- Obtain powerful items to equip your General and army!
- Quest to learn the secrets of alchemy and ancient spells.



Play this game at:
http://apps.facebook.com/castle_age/index.php?bm=1

Come visit us in Castle Age Forum at:
http://www.castleageforums.com/cforum

View our Privacy Policy at:
http://web.castleagegame.com/castle/priv_policy.html

To Join My Castle Age Army!
http://apps.facebook.com/castle_age//index.php?tp=cht&lka=1402408591&buf=1

To Join My Castle Age Elite Guard!
http://apps.facebook.com/castle_age/party.php?twt=jneg&jneg=true&user=1402408591&lka=1402408591&ref=nf

»» Readmore

Wednesday, January 4, 2012

How a Disk Boot Works

by Ron White

A personal computer can’t do anything useful unless it’s running an operating system—a basic type of software that acts as a supervisor for all the applications, games, or other programs you use. The operating system sets the rules for using memory, drives, and other parts of the computer.

But before a PC can run an operating sys tem, it needs some way to load the operating system from disk to random access memory (RAM). The way to do this is with the boot strap or simply to boot — a small amount of code that’s permanently a part of the PC.

The bootstrap is aptly named because it lets the PC do something entirely on its own, without any outside operating system. Of course, the boot operation doesn’t do much. In fact, it has only two functions: one is to run a POST, or power-on self-test described in the preceding chapter, and the other is to search drives for an operating system. When these functions are complete, the boot operation launches the process of reading the system files and copying them to random access memory.

Why do PCs use such a round - about arrangement? Why not simply make the opera ting system a part of the PC? A few low-end or specialized computers do this. Early computers used primarily for playing games, such as the Atari 400 and 800, and the more recent palm-sized PCs, have a permanent operating system. But in most cases, the operating system is loaded from harddisk for two reasons.

It is simpler to upgrade the operating system when loading from a disk. When a company such as Microsoft—which makes MS-DOS and Windows, the most commonly used PC operating systems—wants to add new features or fix serious bugs, it can simply issue a new set of disks. Sometimes all that’s necessary is a single file that patches a flaw in the operating system. It’s cheaper for Microsoft to distribute an operating system on disk than to design a microchip that contains the operating system. And it’s easier for computer users to install a new operating system from disk than it is to swap chips.

The other reason for loading an operating system from disk is that it gives users a choice of operating systems. Although most PCs based on microprocessors built by Intel use Windows or MS-DOS, there are alternative operating systems, such as Windows NT, OS/2, DRDOS, and UNIX. In some PC setups, you can even choose which of the operating systems to use each time you turn on your computer. We’ll use DOS/Windows here because it’s typical of all operating systems.

Disk Boot

1. After conducting a POST check of all the hardware components of a PC, the boot program contained on the computer’s ROM BIOS chips checks drive A to see if it contains a formatted floppy disk. If a disk is mounted in the drive, the program searches specific locations on the disk for the files that make up the first two parts of the operating system. You won’t ordinarily see these system files because each is marked with a special file attribute that ordinarily hides it from any file listing. For Windows systems, the files are named IO.SYS and MSDOS.SYS. If the floppy drive is empty, the boot program checks the hard drive C for the system files, and on some systems, as a last resort, checks the CD-ROM drive. If a boot disk does not contain the files, the boot program generates an error message.

2. After locating a disk with the system files, the boot program reads the data stored on the disk’s first sector and copies that data to specific locations in RAM. This information constitutes the boot record. The boot record is found in the same location on every formatted disk. The boot record is only about 512 bytes, just enough code to initiate the loading of the two hidden system files. After the BIOS boot program has loaded the boot record into memory at the hexadecimal address 7C00, the BIOS passes control to the boot record by branching to that address.

3. The boot record takes control of the PC and loads IO.SYS into RAM. The IO.SYS file contains extensions to the ROM BIOS and includes a routine called SYSINIT that manages the rest of the boot up. After loading IO.SYS, the boot record is no longer needed and is replaced in RAM by other code.

4. SYSINIT assumes control of the start-up process and loads MSDOS.SYS into RAM. The MSDOS.SYS file works with the BIOS to manage files, execute programs, and respond to signals from hardware.

5. SYSINIT searches the root dire c t o ry of the boot disk for a file named CONFIG.SYS. If CONFIG.SYS exists, SYSINIT tells MSDOS.SYS to execute the commands in the file. CONFIG.SYS is a file created by the user. Its commands tell the operating system how to handle certain operations, such as how many files may be opened at one time. CONFIG.SYS may also contain instructions to load device drivers.

Device drivers are files containing code that extends the capabilities of the BIOS to control memory or hardware devices. (In Windows, drivers are loaded through records in a file called the Registry.)

6. SYSINIT tells MSDOS.SYS to load the file COMMAND.COM. This operating system file consists of three parts. One is a further extension to the input/output functions. This part is loaded in memory with the BIOS and becomes a part of the operating system.

7. The second part of COMMAND.COM contains the internal DOS commands such as DIR, COPY, and TYPE. It is loaded at the high end of conventional RAM, where it can be overwritten by applications programs if they need the memory.

8. The third part of COMMAND.COM is used only once and then discarded. This part searches the root directory for a file named AUTOEXEC.BAT. This file is created by the computer’s user and contains a series of DOS batch file commands and/or the names of programs that the user wants to run each time the computer is turned on. The PC is now fully booted and ready to be used.


»» Readmore

Revolver Maps