Posts

Showing posts from January 22, 2010

Overview of Software Engineering Education Knowledge

This chapter describes the body of knowledge that is appropriate for an undergraduate program in software engineering. The knowledge is designated as the SEEK (Software Engineering Education Knowledge). 1. Process of Determining the SEEK The development model chosen for determining SE2004 was based on the model used to construct the CCCS volume. The initial selection of the SEEK areas was based on the SWEBOK knowledge areas and multiple discussions with dozens of SEEK area volunteers. The SEEK area volunteers were divided into groups representing each individual SEEK area, where each group contained roughly seven volunteers. These groups were assigned the task of providing the details of the units that compose a particular educational knowledge area and the further refinement of these units into topics. To facilitate their work, references to existing related software engineering body of knowledge efforts (e.g. SWEBOK, CSDP Exam, and SEI curriculum recommendations) and a set of te

NETWORK BACKUP

Items to do when considering network backups. l. Set a backup schedule 2. Determine data to be backed up and its importance to determine a backup schedule. 3. Determine backup methods, media, and equipment to use. Backup methods include full backup, file copy, backup changed files without marking files as backed up (differential backup), or backup only the files that have changed since the last backup and mark them as backed up (incremental backup). 4. Determine where to store backup information such as a safe. 5.Test the backup and restore capability of the backup system and its media to be sure it reallyworks. 6. Maintain backup logs. 7. Create and maintain a disaster recover plan. Rotate tapes so you could recover your data if your server room or main place of operations was destroyed.

Network Operating Systems

Network operating systems (NOS) typically are used to run computers that act as servers. They provide the capabilities required for network operation. Network operating systems are also designed for client computers and provide functions so the distinction between network operating systems and stand alone. operating systems is not always obvious. Network operating systems provide the following functions: l File and print sharing. l Account administration for users. l Security. Installed Components l Client functionality l Server functionality Functions provided: l Account Administration for users l Security l File and print sharing Network services l File Sharing l Print sharing l User administration l Backing up data Universal Naming Convention (UNC) A universal naming convention (UNC) is used to allow the use of shared resources without mapping a drive to them. The UNC specifies a path name and has the form: \\servername\pathname If I have a Linux server called &