This document is a software requirement specification for a department calendar (DepTCal) system for the Informatics Department at Sepuluh Nopember Institute of Technology. It outlines 9 key functions of the system: viewing the calendar, agenda, schedule details, editing schedules, deleting schedules, creating schedules, adding participants, viewing notifications, and creating users. For each function, it provides user scenarios, activity diagrams, sequence diagrams, and collaboration diagrams to illustrate system requirements.
This document is the project report for a Crime Portal System submitted for a Master's degree. It describes the development of an online portal that allows citizens to report crimes, search for missing persons, and view details on criminals. The system will facilitate communication between stakeholders like citizens, police departments, and the defense. It includes modules for administration, user complaints, criminal records, news, and more. The report discusses the existing system, proposed new system, feasibility analysis, design of the portal using data flow diagrams and ER modeling, and implementation using Java and related technologies.
This document provides an overview of the Candy Construction Estimating and Valuations user interface and navigation. It describes the main sections of the user interface including the title bar, application tabs, menus and toolbars. It also explains how to navigate between documents and use various keyboard shortcuts and right-click menu functions. The document concludes with information on customizing system fonts, colors, toolbars and configuring folder paths.
This document provides an index and overview of the chapters contained in the Candy Construction Planning & Programming course notes. The chapters cover topics like starting a new company and job in Candy, using the planning and calendar modules, creating and customizing bar charts to plan activities, program analysis using checklists and timelines, reporting on resources, procurement scheduling, and updating progress. The course aims to teach the objectives and logic of Candy planning as well as practical techniques for filtering, sorting, copying and navigating documents.
Candy - Construction Estimating & Valuations - rev 2.01Jerico Awat
This document provides a table of contents for a course on construction estimating and valuations. The document outlines 12 chapters that will be covered in the course, including importing a bill of quantities, pricing bill items, using subcontractors, adding markups, and post-tender control. Key topics that will be addressed include downloading software, setting up new projects, importing Excel spreadsheets, defining trades, using worksheets to price items, analyzing resources, and using masters for pricing.
The document summarizes discussions from a 1968 NATO conference on software engineering. Key topics discussed include:
- The challenges of developing large, complex software projects that must be reliable, meet specifications and deadlines.
- Different approaches to designing software, including sequencing the design process, structuring the design, and using feedback and simulation.
- Managing large production efforts for software, which face problems of scale, reliability, planning, personnel, and control.
- Distributing, maintaining, and evaluating software after initial release to users through replication, distribution, and acceptance testing.
The conference aimed to address the fundamental issues and challenges in software engineering at the time.
Reports Wizard - free application for reporting in IBM ( Lotus ) Notes / Dominonotesapps.org
The application Reports Wizard allows you to create reports using data from documents of databases IBM Lotus Notes® ( NSF ). Once describe in the application the data sources based on documents in databases, as well as their attributes and relations, and then apply them when creating structures of your reports.
The settings of a data source allow you to perform required data selecting and processing for a report. In addition to it, large amount of settings for reporting and data exporting give to you possibility to create reports of various complexity with result which doesn't require any additional processing, and this is without of using a programming language.
Obvious report structures can be understandable for a user with minimum skills in IT, to allow him himself to create and change his reports in the application.
Full info and download on notesapps.org
This document is the user manual for CodeVisionAVR version 1.25.8. It begins with an introduction and overview of the CodeVisionAVR integrated development environment. It then describes how to work with files, projects, and tools within the IDE. The next sections provide a reference for the CodeVisionAVR C compiler and included library functions. The final sections describe the CodeWizardAVR automatic program generator and include licensing information, technical support details, and contact information.
MEASURING THE POST OCCUPANCY PERFORMANCE OF THE FACULTY OF ENGINEERING BUILDI...Ofentse Matsetse
This document provides a literature review on post-occupancy evaluation (POE). It discusses the history and purpose of POE, noting that POE began in the 1960s to evaluate housing after rapid construction. POE assesses how well buildings meet user needs and identifies ways to improve design, performance, and fitness for purpose. The literature review discusses the benefits of POE in improving building performance and future designs based on user feedback. It also outlines common POE methods and limitations.
This document is the project report for a Crime Portal System submitted for a Master's degree. It describes the development of an online portal that allows citizens to report crimes, search for missing persons, and view details on criminals. The system will facilitate communication between stakeholders like citizens, police departments, and the defense. It includes modules for administration, user complaints, criminal records, news, and more. The report discusses the existing system, proposed new system, feasibility analysis, design of the portal using data flow diagrams and ER modeling, and implementation using Java and related technologies.
This document provides an overview of the Candy Construction Estimating and Valuations user interface and navigation. It describes the main sections of the user interface including the title bar, application tabs, menus and toolbars. It also explains how to navigate between documents and use various keyboard shortcuts and right-click menu functions. The document concludes with information on customizing system fonts, colors, toolbars and configuring folder paths.
This document provides an index and overview of the chapters contained in the Candy Construction Planning & Programming course notes. The chapters cover topics like starting a new company and job in Candy, using the planning and calendar modules, creating and customizing bar charts to plan activities, program analysis using checklists and timelines, reporting on resources, procurement scheduling, and updating progress. The course aims to teach the objectives and logic of Candy planning as well as practical techniques for filtering, sorting, copying and navigating documents.
Candy - Construction Estimating & Valuations - rev 2.01Jerico Awat
This document provides a table of contents for a course on construction estimating and valuations. The document outlines 12 chapters that will be covered in the course, including importing a bill of quantities, pricing bill items, using subcontractors, adding markups, and post-tender control. Key topics that will be addressed include downloading software, setting up new projects, importing Excel spreadsheets, defining trades, using worksheets to price items, analyzing resources, and using masters for pricing.
The document summarizes discussions from a 1968 NATO conference on software engineering. Key topics discussed include:
- The challenges of developing large, complex software projects that must be reliable, meet specifications and deadlines.
- Different approaches to designing software, including sequencing the design process, structuring the design, and using feedback and simulation.
- Managing large production efforts for software, which face problems of scale, reliability, planning, personnel, and control.
- Distributing, maintaining, and evaluating software after initial release to users through replication, distribution, and acceptance testing.
The conference aimed to address the fundamental issues and challenges in software engineering at the time.
Reports Wizard - free application for reporting in IBM ( Lotus ) Notes / Dominonotesapps.org
The application Reports Wizard allows you to create reports using data from documents of databases IBM Lotus Notes® ( NSF ). Once describe in the application the data sources based on documents in databases, as well as their attributes and relations, and then apply them when creating structures of your reports.
The settings of a data source allow you to perform required data selecting and processing for a report. In addition to it, large amount of settings for reporting and data exporting give to you possibility to create reports of various complexity with result which doesn't require any additional processing, and this is without of using a programming language.
Obvious report structures can be understandable for a user with minimum skills in IT, to allow him himself to create and change his reports in the application.
Full info and download on notesapps.org
This document is the user manual for CodeVisionAVR version 1.25.8. It begins with an introduction and overview of the CodeVisionAVR integrated development environment. It then describes how to work with files, projects, and tools within the IDE. The next sections provide a reference for the CodeVisionAVR C compiler and included library functions. The final sections describe the CodeWizardAVR automatic program generator and include licensing information, technical support details, and contact information.
MEASURING THE POST OCCUPANCY PERFORMANCE OF THE FACULTY OF ENGINEERING BUILDI...Ofentse Matsetse
This document provides a literature review on post-occupancy evaluation (POE). It discusses the history and purpose of POE, noting that POE began in the 1960s to evaluate housing after rapid construction. POE assesses how well buildings meet user needs and identifies ways to improve design, performance, and fitness for purpose. The literature review discusses the benefits of POE in improving building performance and future designs based on user feedback. It also outlines common POE methods and limitations.
The document is an operator manual for the Interactive Channel Platform (ICP) interactive television system. It provides instructions for ICP operators to manage the system and support user experiences. The manual contains tutorials on the basics of interactive TV and using the ICP. It also includes reference sections on monitoring, configuring, updating, starting/stopping the system, and troubleshooting. Appendices provide additional technical details.
This document describes a project to develop an online notice board system for Adigrat University. It includes signatures and details of the student group developing the project. It outlines the project objectives, which are to design and implement a system for posting, viewing, and managing notices online. The document also discusses the data collection and design methodologies, including use of interviews, observations, and an object-oriented approach. It evaluates the technical, economic and time feasibility of the project. Finally, it explains the significance of the project in reducing costs and improving information dissemination for the university.
E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATIONPIYUSH Dubey
Hello Friends, This online web application project E-FREELANCING, I made during my Engineering days. But couldn't upload. But seeing the greater demand for project documentations, I have finally uploaded this. Kindly review and let me know if this helps you. Reach out to me on masterpiyushdubey@gmail.com if you want this documentation .
This document provides an overview and guidelines for developing applications using Oracle Applications Release 11i. It discusses setting up the application framework, including directory structures and registering the application. It also covers building database objects and the standard development environment. The document contains three chapters that describe setting up the application framework, building database objects, and coding standards.
This document is a user manual for the TX16Wx software sampler. It describes the sampler's sound architecture including banks, performances, programs, groups, splits and waves. It provides details on the user interface and how to use the various views and editors for selecting sounds, editing programs and samples, and configuring overall settings. Key features covered include the performance view for managing multitimbral setups, the program editor for mapping samples, and the wave editor for sample playback and editing.
Information Technology Disaster Recovery Guide - ABC Bank (redacted)Stephen White
This document provides a disaster recovery guide for ABC Bank. It outlines ABC Bank's current IT infrastructure, which includes servers and applications located across multiple sites. It then details the objectives, risks, preparation, and procedures for recovering ABC Bank's IT systems and services in the event of a disaster that impacts the primary data center. The plan defines the disaster recovery team and processes for activating the plan, assessing damage, restoring backups, and recovering critical systems and applications from the disaster recovery site.
This document provides an overview of Oracle Receivables functionality including setting up parties, transactions, processing invoices, payments, and adjustments. It discusses key areas like defining setup options, entering transactions, completing invoices, correcting errors, applying receipts, processing commitments, and remitting customer payments. The overview explains the various transaction types, accounting rules, payment methods, and status updates available within Oracle Receivables.
This document provides an overview of SQL concepts and Oracle Applications. It includes classifications of SQL commands like tables, views, sequences and explain plans. It also covers PL/SQL concepts such as block structure, cursors, exceptions, procedures, functions, packages and triggers. The document discusses Oracle Applications, ERP methodology, database structure, file architecture and entering data into Oracle Applications.
This document provides an overview of the H-SPIS v4.0 MIS platform for the informal sector in 3 pages. It includes a table of contents that lists 9 main sections that describe the system's functionality for members, utilization/claims, providers, operators, tools, reporting, and settings. The platform allows operators to manage member households, contracts, premium collection, benefits, and medical utilization. It also facilitates cashless and cash-based claims processing with providers. Detailed reports and analytics tools are available to monitor operations and utilization.
This document describes the interface boards used in SOPHO iS3000 Series PBX systems. It discusses analogue line circuits like the ALC-A/B, ALC-E, ALC-F and ALC-G, which provide interfaces between analogue phone lines and the PBX. Settings for switches and straps on these boards determine aspects like the number of line interfaces and transmission protocols. The document also covers other board types like digital line circuits, trunk units and control boards.
This document outlines the knowledge required to pass the Information Technology Engineers Examination in Japan. It is organized into 9 major categories covering topics such as corporate strategy, business strategy, system strategy, development technology, project management, and basic computer science theory. Each major category contains multiple middle categories that further break down the knowledge into specific items. For each item, the document provides a goal statement describing what should be learned and descriptions with sample terms and examples. The purpose is to guide examinees in their preparation and provide instructional guidelines for companies and schools.
PRINCE2 is a project management methodology that provides principles, processes, and techniques. It is divided into seven processes: starting up a project, initiating a project, directing a project, controlling a stage, managing product delivery, managing stage boundaries, and closing a project. Each process contains activities to be performed with defined inputs and outputs. The methodology also includes components like the business case, organization, plans, controls, risk management, quality, and configuration management. PRINCE2 provides a structured approach to project management with an emphasis on dividing projects into manageable and controlled stages.
This document provides an overview and contents of an IT Passport exam preparation book. The book covers a wide range of topics related to IT strategy, management, technology, and systems. It is divided into 9 chapters that cover areas such as corporate and legal affairs, business strategy, system strategy, development technology, project management, service management, basic theory, computer systems, and technology elements. Each chapter contains multiple sections that delve deeper into the various subtopics within each area.
This document announces a two-step Broad Agency Announcement (BAA) for the Air Force FY 2013 Rapid Innovation Fund (RIF) program. It provides information on program objectives, submission requirements and schedules, evaluation criteria, and anticipated funding. The goal is to fund innovative technologies that address critical Air Force needs outlined in an attachment, with up to 25 awards totaling $45-65 million expected. The first step requires submission of white papers by October 8, 2013. Invited offerors will then submit full proposals which will be evaluated starting in December 2013.
This document provides an overview and instructions for using the Atlas user interface. It outlines the main tabs for partner setup, administration, sales orders, service orders, workflows, customers, and email management. Sections describe how to configure partner details, manage users and permissions, import and reserve phone numbers, create and modify sales order proposals, approve discounts, and track order statuses. The document also includes examples of automated emails sent to customers and partners at different stages of the sales process.
This document is the system administrator's guide for Oracle Applications Release 11 from March 1998. It provides information to administrators for managing Oracle Applications security, user and data auditing, help, user profiles, concurrent programs and reports, concurrent processing, printers, and other system administration tasks. The guide includes descriptions of configuration windows, reports, and other tools to help administrators set up and manage the Oracle Applications system. It contains chapters on security, auditing, help, profiles, concurrent processing, and printers.
Manajemen ruang lingkup proyek meliputi proses mendefinisikan dan mengontrol cakupan pekerjaan yang termasuk dan tidak termasuk dalam proyek untuk memastikan keberhasilannya. Proses ini meliputi inisiasi proyek, perencanaan ruang lingkup, definisi ruang lingkup, verifikasi ruang lingkup, dan pengendalian perubahan ruang lingkup.
The document is an operator manual for the Interactive Channel Platform (ICP) interactive television system. It provides instructions for ICP operators to manage the system and support user experiences. The manual contains tutorials on the basics of interactive TV and using the ICP. It also includes reference sections on monitoring, configuring, updating, starting/stopping the system, and troubleshooting. Appendices provide additional technical details.
This document describes a project to develop an online notice board system for Adigrat University. It includes signatures and details of the student group developing the project. It outlines the project objectives, which are to design and implement a system for posting, viewing, and managing notices online. The document also discusses the data collection and design methodologies, including use of interviews, observations, and an object-oriented approach. It evaluates the technical, economic and time feasibility of the project. Finally, it explains the significance of the project in reducing costs and improving information dissemination for the university.
E-FREELANCING - MAJOR/FINAL YEAR PROJECT DOCUMENTATIONPIYUSH Dubey
Hello Friends, This online web application project E-FREELANCING, I made during my Engineering days. But couldn't upload. But seeing the greater demand for project documentations, I have finally uploaded this. Kindly review and let me know if this helps you. Reach out to me on masterpiyushdubey@gmail.com if you want this documentation .
This document provides an overview and guidelines for developing applications using Oracle Applications Release 11i. It discusses setting up the application framework, including directory structures and registering the application. It also covers building database objects and the standard development environment. The document contains three chapters that describe setting up the application framework, building database objects, and coding standards.
This document is a user manual for the TX16Wx software sampler. It describes the sampler's sound architecture including banks, performances, programs, groups, splits and waves. It provides details on the user interface and how to use the various views and editors for selecting sounds, editing programs and samples, and configuring overall settings. Key features covered include the performance view for managing multitimbral setups, the program editor for mapping samples, and the wave editor for sample playback and editing.
Information Technology Disaster Recovery Guide - ABC Bank (redacted)Stephen White
This document provides a disaster recovery guide for ABC Bank. It outlines ABC Bank's current IT infrastructure, which includes servers and applications located across multiple sites. It then details the objectives, risks, preparation, and procedures for recovering ABC Bank's IT systems and services in the event of a disaster that impacts the primary data center. The plan defines the disaster recovery team and processes for activating the plan, assessing damage, restoring backups, and recovering critical systems and applications from the disaster recovery site.
This document provides an overview of Oracle Receivables functionality including setting up parties, transactions, processing invoices, payments, and adjustments. It discusses key areas like defining setup options, entering transactions, completing invoices, correcting errors, applying receipts, processing commitments, and remitting customer payments. The overview explains the various transaction types, accounting rules, payment methods, and status updates available within Oracle Receivables.
This document provides an overview of SQL concepts and Oracle Applications. It includes classifications of SQL commands like tables, views, sequences and explain plans. It also covers PL/SQL concepts such as block structure, cursors, exceptions, procedures, functions, packages and triggers. The document discusses Oracle Applications, ERP methodology, database structure, file architecture and entering data into Oracle Applications.
This document provides an overview of the H-SPIS v4.0 MIS platform for the informal sector in 3 pages. It includes a table of contents that lists 9 main sections that describe the system's functionality for members, utilization/claims, providers, operators, tools, reporting, and settings. The platform allows operators to manage member households, contracts, premium collection, benefits, and medical utilization. It also facilitates cashless and cash-based claims processing with providers. Detailed reports and analytics tools are available to monitor operations and utilization.
This document describes the interface boards used in SOPHO iS3000 Series PBX systems. It discusses analogue line circuits like the ALC-A/B, ALC-E, ALC-F and ALC-G, which provide interfaces between analogue phone lines and the PBX. Settings for switches and straps on these boards determine aspects like the number of line interfaces and transmission protocols. The document also covers other board types like digital line circuits, trunk units and control boards.
This document outlines the knowledge required to pass the Information Technology Engineers Examination in Japan. It is organized into 9 major categories covering topics such as corporate strategy, business strategy, system strategy, development technology, project management, and basic computer science theory. Each major category contains multiple middle categories that further break down the knowledge into specific items. For each item, the document provides a goal statement describing what should be learned and descriptions with sample terms and examples. The purpose is to guide examinees in their preparation and provide instructional guidelines for companies and schools.
PRINCE2 is a project management methodology that provides principles, processes, and techniques. It is divided into seven processes: starting up a project, initiating a project, directing a project, controlling a stage, managing product delivery, managing stage boundaries, and closing a project. Each process contains activities to be performed with defined inputs and outputs. The methodology also includes components like the business case, organization, plans, controls, risk management, quality, and configuration management. PRINCE2 provides a structured approach to project management with an emphasis on dividing projects into manageable and controlled stages.
This document provides an overview and contents of an IT Passport exam preparation book. The book covers a wide range of topics related to IT strategy, management, technology, and systems. It is divided into 9 chapters that cover areas such as corporate and legal affairs, business strategy, system strategy, development technology, project management, service management, basic theory, computer systems, and technology elements. Each chapter contains multiple sections that delve deeper into the various subtopics within each area.
This document announces a two-step Broad Agency Announcement (BAA) for the Air Force FY 2013 Rapid Innovation Fund (RIF) program. It provides information on program objectives, submission requirements and schedules, evaluation criteria, and anticipated funding. The goal is to fund innovative technologies that address critical Air Force needs outlined in an attachment, with up to 25 awards totaling $45-65 million expected. The first step requires submission of white papers by October 8, 2013. Invited offerors will then submit full proposals which will be evaluated starting in December 2013.
This document provides an overview and instructions for using the Atlas user interface. It outlines the main tabs for partner setup, administration, sales orders, service orders, workflows, customers, and email management. Sections describe how to configure partner details, manage users and permissions, import and reserve phone numbers, create and modify sales order proposals, approve discounts, and track order statuses. The document also includes examples of automated emails sent to customers and partners at different stages of the sales process.
This document is the system administrator's guide for Oracle Applications Release 11 from March 1998. It provides information to administrators for managing Oracle Applications security, user and data auditing, help, user profiles, concurrent programs and reports, concurrent processing, printers, and other system administration tasks. The guide includes descriptions of configuration windows, reports, and other tools to help administrators set up and manage the Oracle Applications system. It contains chapters on security, auditing, help, profiles, concurrent processing, and printers.
Manajemen ruang lingkup proyek meliputi proses mendefinisikan dan mengontrol cakupan pekerjaan yang termasuk dan tidak termasuk dalam proyek untuk memastikan keberhasilannya. Proses ini meliputi inisiasi proyek, perencanaan ruang lingkup, definisi ruang lingkup, verifikasi ruang lingkup, dan pengendalian perubahan ruang lingkup.
Sistem Informasi Koperasi Karyawan Stikom Surabaya bertujuan untuk meningkatkan efisiensi dan transparansi proses simpan pinjam serta manajemen koperasi secara keseluruhan dengan menggunakan sistem berbasis komputer. Proyek ini akan menghasilkan dokumen desain sistem, spesifikasi perangkat lunak, arsitektur sistem, rencana pengujian, dan dokumentasi pengguna. Proyek ini dijadwalkan selesai pada Desember 2011 dengan anggar
Dokumen ini memberikan ringkasan eksekutif proyek studi program S1 Sistem Informasi. Ringkasan ini mencakup tujuan proyek, kasus bisnis, deskripsi proyek, risiko, anggaran, persyaratan persetujuan, dan tanggung jawab manajer proyek. Dokumen ini bertujuan memberikan gambaran umum proyek sebelum disetujui.
Studi kelayakan proyek perangkat lunak bertujuan untuk menilai kelayakan teknis, operasional, dan ekonomis proyek dengan mengumpulkan data melalui wawancara, kuesioner, dan observasi, serta mengevaluasi cakupan masalah, biaya estimasi, dan kelayakan solusi yang diusulkan. Langkah-langkahnya meliputi pengumpulan data, studi kelayakan awal, perencanaan proyek, dan persetujuan.
Dokumen tersebut membahas pentingnya rencana proyek yang terdiri atas perencanaan ruang lingkup, waktu, kualitas, organisasi, biaya, komunikasi, dan manajemen resiko guna menyelesaikan proyek dengan menjadwalkan sumber daya, menentukan tahapan utama, memperkirakan anggaran, dan menyusun kerangka kerja pengukuran.
Political Alert - House of Representatives Daily Program (FED)Lisa Munoz
The document outlines the agenda for proceedings in the Australian House of Representatives and Federation Chamber on Monday, 27 March 2017. It includes:
1. Presentation and debate of committee reports in the House, including on biosecurity of Australian honey bees.
2. Presentation of a private member's bill on establishing a banking code of conduct and another establishing an inquiry into banking and financial services.
3. Debate on several motions in the Federation Chamber covering topics like multiculturalism, water infrastructure, penalty rates, and supporting small businesses.
4. Continuing consideration of government bills in the House related to therapeutic goods and enterprise tax plans.
This document provides information about purchasing a 3Com 3C63414-8EI product from Launch 3 Telecom. It describes the product, details how to purchase it through various methods, and outlines Launch 3 Telecom's shipping, warranty, repair, and other telecom services. Launch 3 Telecom is an expert seller and service provider of 3Com and other telecom equipment.
This document provides information about purchasing a 3Com 3C16471B / 10016355 Baseline 2024 24 Ports device. It details how to purchase the device through their website or by phone, as well as their payment and shipping options. The document also provides information about the warranty, repair services, and other services available from Launch 3 Telecom.
This document provides information about purchasing a 3Com 7030-10067 software license. It can be purchased by calling or emailing the company, Launch 3 Telecom. Launch 3 Telecom specializes in telecom equipment and provides services like installation, repair, and asset recovery. The product will be shipped the same day if ordered before 3pm, and includes a warranty and return policy.
Este documento presenta información sobre diferentes temas de psicología como la psicología educativa, la psicología clínica, la psicología social, las formas de aprendizaje, la motivación, la autoestima y las teorías del conductismo, cognitivismo y constructivismo. Explica conceptos clave de cada tema y menciona teóricos importantes como Jean Piaget y sus etapas del desarrollo cognitivo. El documento parece ser apuntes de una clase introductoria a la psicología que resume los principales aspect
El Centro de Excelencia Deportiva Profesor Alberto Byas se encuentra en San Pedro de Macorís y tiene como objetivo lograr la participación e integración de los padres, madres, amigos y tutores en sus actividades. Su misión es brindar una educación integral de excelente calidad con énfasis en la formación deportiva basada en valores como la responsabilidad, el respeto y la honestidad. Su visión es ser un centro educativo que promueva el buen funcionamiento individual y colectivo de sus estudiantes. El centro cuenta con instalaciones como aulas, laborator
Purple parrots westing game character profilesajroets
This document contains character profiles from The Westing Game that are mostly blank. It provides some initial information about a few characters: Samuel Westing is described as being old and dead; Turtle Wexler's physical description includes a still blank face with pale skin and blue eyes, and that she is getting married to Dr. Deere; Chris Theodorakis dared his little brother Theo to go in the Westing house. However, most of the profiles do not include any physical descriptions, information on what is initially learned about the characters, or what is learned about them throughout the story.
A Mobile and Web application for time measurement intended to get an accurate picture of the productive time in a production environment in order to reveal the root causes behind ineffective/idle time and to eliminate non-added activities/tasks .
Technical Key-words : Ionic 2, Angular 2, PouchDB, CouchDB ,
DB Replication Protocol, Django, Python NvD3 charts .
Ensuring Distributed Accountability in the CloudSuraj Mehta
Ensuring distributed accountability for data sharing in the cloud is in short nothing
but a novel highly decentralized information accountability framework to keep track
of the actual usage of the users' data in the cloud. Cloud computing enables highly
ecient services that are easily consumed over the internet.
This document is a project report that proposes developing a web application to securely store files on a cloud server using hybrid cryptography. It aims to address data security and privacy issues for cloud storage. The application would use a hybrid cryptography technique combining symmetric and asymmetric encryption to encrypt files before uploading them to the cloud. Only authorized users with decryption keys would be able to access and download encrypted files from the cloud server. The report outlines the problem statement, objectives, methodology, design, and implementation of the proposed application to provide secure file storage on the cloud.
The document discusses a 2002 master's thesis titled "Incorporating Aspects into the Software Development Process in the Context of Aspect-Oriented Programming". The thesis proposes ways to model aspects using the Unified Modeling Language (UML) during software development. It reviews research on aspect-oriented programming and the software development process. It then presents proposals for incorporating aspects into the Unified Process phases and using UML diagrams like use case diagrams, class diagrams, and interaction diagrams to model cross-cutting concerns. The goal is to support aspect-oriented thinking throughout the software lifecycle.
This document is the beginner's manual for MELSOFT GX IEC Developer version 7.01. It provides an introduction to programming and documentation using the GX IEC Developer IEC 61131-3 programming software. The manual explains basic terms used in IEC 61131-3 such as projects, program organisation units, variables, and programming languages. It also covers installation of the software and describes the user interface. The document concludes with steps for getting started with programming using GX IEC Developer.
This document describes the design and implementation of a 16-bit RISC processor based on Harvard architecture using an FPGA. The processor design uses a finite state machine approach and consists of four main modules - the Arithmetic Logic Unit (ALU), control unit, datapath and processing unit. The ALU, control unit and datapath modules are modeled in Verilog HDL and their functionalities are verified through simulation using Xilinx ISE design tools. The processor is synthesized for implementation on a target FPGA.
This document is a minor project report submitted by Shahrukh Mohd Ayyaz Khan to the Department of Computer Engineering at SSBT's College of Engineering and Technology in partial fulfillment of the requirements for a Bachelor of Engineering degree. The report details the development of a Local Area Network Manager application. It includes sections on system analysis, requirements specification, system design, implementation, testing, results and analysis, and conclusions. Diagrams and screenshots are provided to illustrate various aspects of the system architecture, design, and functionality.
The use of synchrophasors for monitoring and improving the stability of power transmission networks is gaining in significance all over the world. The aim is to monitor the system state, to intensify awareness for system stability and to make optimal use of existing lines. This way, system stability can be improved overall and even the transmission performance can be increased. The data from so many PMU’s and PDC’s needs to be collected and directed to proper channels for its efficient use. Thus we need to develop an efficient, flexible and hybrid data concentrator that can serve this purpose. Besides accepting the data from PMU’s, PDC should be able to accept the data also from other PDC. We have designed such a PDC (iPDC) that accepts data from PMU & PDC that are IEEEC37.118 standard compliant.
WAMS architecture with iPDC and PMU at different levels. This architecture enables iPDC to receive data either from a PMU or other iPDC. Both PMU and iPDC from whom the data is being received should be IEEE C37.118 synchrophasor standard compliant. It is hybrid architecture.
iPDC Design
The client server architecture is common in networks when two peers are communicating with each other. Of the two peers (PMU and iPDC) that are communicating with each other in WAMS one acts as a client and the other as a server. Since PMU saves the requests coming
from iPDC by sending data or configuration frames it acts as a server. It listens for command frames from iPDC. PMU-iPDC communication can be either over TCP or UDP communication protocols. On receiving command frames, PMU replies to the iPDC with data or configuration frames according to the type of request.
iPDC functionality is bifurcated as server and client. iPDC as a Client - When iPDC receives data or configuration frames its acts as a client. When acting as a client, it creates a new thread for each PMU or a PDC from whom it is going to receive data/configuration frames. This thread would establish connection between the two communication entities. It handles both TCP and UDP connections. The first frame that the server (PMU/PDC) would receive is the command for sending the configuration frame. When the server replies with the configuration frame, iPDC (client) would generate another request to start sending the data frames. On receiving
such a command frame, the server starts sending the data frames. If there is some change in the status bits of data frame which the client (iPDC) notices, it would take an action. For example if it notices a bit 10 has been set, it would internally send a command to server to send the latest configuration frame.
iPDC as a Server- When iPDC receives command frames from another PDC it would acts as a server. There would be two reserved ports one for UDP and other for TCP on which the PDC would receive command frame requests. Thus PDC now plays the role of PMU waiting
for command frames.
This document outlines test requirements for testing a remote radio head module. It describes test cases to verify the transmitter and receiver functionality. Transmitter tests include output power, EVM, frequency accuracy, and spectrum mask tests. Receiver tests include noise figure, blocking, and dynamic range tests. The document specifies the required test equipment, setup, and procedures to automate calibration and performance testing of the radio module.
The document provides a Software Project Management Plan (SPMP) for developing software for Nirvana National Bank's ATM project. It outlines the project scope, objectives, assumptions, constraints, deliverables, schedule and budget. The SPMP will guide Terasoft's project manager and participants in conducting the software development effort. It describes start-up, work, control, technical, and supporting plans and processes to be followed. The SPMP establishes the initial project baseline and defines how it will be updated and changed over time. It also references various project documents and IEEE software engineering standards that will be adhered to.
Report on e-Notice App (An Android Application)Priyanka Kapoor
The document is a report submitted for a degree at DigiMantra Labs, Ludhiana from January 5, 2014 to May 30, 2014. It describes the development of an e-Notice Application for Android phones. The app allows users to access online notices on their phone and acts as an online notice board where people can communicate and post notices with text, images or videos. It aims to digitize the traditional notice board and allow staff/students to read and respond to notices from anywhere. The app also serves as a mailing list to notify all employees of new notices without needing to maintain a separate mailing list.
This document provides a draft software requirements specification for the Interactive Logbook project. It includes an introduction, overall description of the product and its features, user requirements for the .NET client and Java 2 Micro Edition client, and system features. The document outlines requirements for document handling, audio/video recording, writing with a stylus, collaboration features like file sharing and messaging, text editing, printing, search, study aids, help features, and integration with institutional systems. It also describes the user classes, operating environments, design constraints, and assumptions.
This document describes a project to design and implement an OFDM-based wireless transmitter compliant with the IEEE 802.11g standard on an FPGA. The transmitter was modeled using Simulink and the model was tested through cosimulation and using EDA tools. Testing showed the design met timing requirements and error measurements were satisfactory, demonstrating a successful OFDM transmitter design using a model-based approach.
The document is a project report submitted by Kedar Khandeparkar for the partial fulfillment of the requirements for the degree of Master of Technology. It discusses the design and implementation of communication, storage, and archival of an IEEE C37.118 standard based Wide Area Measurement System (WAMS). WAMS uses Phasor Measurement Units (PMUs) to collect synchronized phasor measurements across the power grid to provide improved monitoring capabilities compared to traditional SCADA systems. The report covers the components of WAMS, communication protocols, existing WAMS implementations, and use of databases for storage and archival of PMU/PDC data.
Systems Analysis And Design Methodology And Supporting ProcessesAlan McSweeney
This document outlines the methodology and processes for systems analysis and design. It discusses the project initiation phase which involves setting objectives, scope, benefits, timeline, and costs. It also covers the analysis phase which focuses on requirements gathering and modeling. The enterprise modeling phase is described as developing information models, architectures, and technology plans. Specific project deliverables are provided for each phase.
This document is a lab manual for an introduction to computer programming course using C++. It contains 11 chapters that provide examples and exercises to help students learn programming concepts like variables, operators, control flow, functions, arrays, pointers, structures, and file input/output. Each chapter contains multiple programming questions and examples with the full code provided. The objective is to give students hands-on practice with programming to become familiar with design, coding, and problem solving in C++.
This document provides release notes for Oracle Developer Suite 10g Release 2 (10.1.2) for Solaris, Windows and Linux x86. It includes sections on certification information, known issues, and component release notes. The known issues section documents problems related to installation, configuration, documentation and other areas. The component release notes sections provide additional details on specific issues and limitations for Oracle Business Intelligence Beans, Oracle Forms, and other Developer Suite components.
This document describes using open source tools for cross development on ST microcontrollers from the STR710, STR730 and STR750 families. It discusses the necessary hardware, including a target board with the microcontroller, a JTAG interface to connect the board to a PC, and the software tools used, such as OpenOCD, GNU ARM Eclipse and Insight. It then provides tutorials for setting up the tools on Windows and Linux, covering installing software, configuring projects, building and debugging programs. Details are given on the configuration files and project template created by the authors to support development. Tests were also done with an STR912 board which showed promising results.
This document provides an overview and guidelines for developing applications using Oracle Forms and PL/SQL. It covers setting up the application framework, building database objects, using PL/SQL, and setting properties of container objects like windows, canvases, and blocks. The document contains information on Oracle Application Object Library classes, coding standards, performance best practices, and examples of coding item, event, and table handlers on both the client and server side.
Applications of artificial Intelligence in Mechanical Engineering.pdfAtif Razi
Historically, mechanical engineering has relied heavily on human expertise and empirical methods to solve complex problems. With the introduction of computer-aided design (CAD) and finite element analysis (FEA), the field took its first steps towards digitization. These tools allowed engineers to simulate and analyze mechanical systems with greater accuracy and efficiency. However, the sheer volume of data generated by modern engineering systems and the increasing complexity of these systems have necessitated more advanced analytical tools, paving the way for AI.
AI offers the capability to process vast amounts of data, identify patterns, and make predictions with a level of speed and accuracy unattainable by traditional methods. This has profound implications for mechanical engineering, enabling more efficient design processes, predictive maintenance strategies, and optimized manufacturing operations. AI-driven tools can learn from historical data, adapt to new information, and continuously improve their performance, making them invaluable in tackling the multifaceted challenges of modern mechanical engineering.
An improved modulation technique suitable for a three level flying capacitor ...IJECEIAES
This research paper introduces an innovative modulation technique for controlling a 3-level flying capacitor multilevel inverter (FCMLI), aiming to streamline the modulation process in contrast to conventional methods. The proposed
simplified modulation technique paves the way for more straightforward and
efficient control of multilevel inverters, enabling their widespread adoption and
integration into modern power electronic systems. Through the amalgamation of
sinusoidal pulse width modulation (SPWM) with a high-frequency square wave
pulse, this controlling technique attains energy equilibrium across the coupling
capacitor. The modulation scheme incorporates a simplified switching pattern
and a decreased count of voltage references, thereby simplifying the control
algorithm.
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...IJECEIAES
Climate change's impact on the planet forced the United Nations and governments to promote green energies and electric transportation. The deployments of photovoltaic (PV) and electric vehicle (EV) systems gained stronger momentum due to their numerous advantages over fossil fuel types. The advantages go beyond sustainability to reach financial support and stability. The work in this paper introduces the hybrid system between PV and EV to support industrial and commercial plants. This paper covers the theoretical framework of the proposed hybrid system including the required equation to complete the cost analysis when PV and EV are present. In addition, the proposed design diagram which sets the priorities and requirements of the system is presented. The proposed approach allows setup to advance their power stability, especially during power outages. The presented information supports researchers and plant owners to complete the necessary analysis while promoting the deployment of clean energy. The result of a case study that represents a dairy milk farmer supports the theoretical works and highlights its advanced benefits to existing plants. The short return on investment of the proposed approach supports the paper's novelty approach for the sustainable electrical system. In addition, the proposed system allows for an isolated power setup without the need for a transmission line which enhances the safety of the electrical network
Null Bangalore | Pentesters Approach to AWS IAMDivyanshu
#Abstract:
- Learn more about the real-world methods for auditing AWS IAM (Identity and Access Management) as a pentester. So let us proceed with a brief discussion of IAM as well as some typical misconfigurations and their potential exploits in order to reinforce the understanding of IAM security best practices.
- Gain actionable insights into AWS IAM policies and roles, using hands on approach.
#Prerequisites:
- Basic understanding of AWS services and architecture
- Familiarity with cloud security concepts
- Experience using the AWS Management Console or AWS CLI.
- For hands on lab create account on [killercoda.com](https://killercoda.com/cloudsecurity-scenario/)
# Scenario Covered:
- Basics of IAM in AWS
- Implementing IAM Policies with Least Privilege to Manage S3 Bucket
- Objective: Create an S3 bucket with least privilege IAM policy and validate access.
- Steps:
- Create S3 bucket.
- Attach least privilege policy to IAM user.
- Validate access.
- Exploiting IAM PassRole Misconfiguration
-Allows a user to pass a specific IAM role to an AWS service (ec2), typically used for service access delegation. Then exploit PassRole Misconfiguration granting unauthorized access to sensitive resources.
- Objective: Demonstrate how a PassRole misconfiguration can grant unauthorized access.
- Steps:
- Allow user to pass IAM role to EC2.
- Exploit misconfiguration for unauthorized access.
- Access sensitive resources.
- Exploiting IAM AssumeRole Misconfiguration with Overly Permissive Role
- An overly permissive IAM role configuration can lead to privilege escalation by creating a role with administrative privileges and allow a user to assume this role.
- Objective: Show how overly permissive IAM roles can lead to privilege escalation.
- Steps:
- Create role with administrative privileges.
- Allow user to assume the role.
- Perform administrative actions.
- Differentiation between PassRole vs AssumeRole
Try at [killercoda.com](https://killercoda.com/cloudsecurity-scenario/)
Embedded machine learning-based road conditions and driving behavior monitoringIJECEIAES
Car accident rates have increased in recent years, resulting in losses in human lives, properties, and other financial costs. An embedded machine learning-based system is developed to address this critical issue. The system can monitor road conditions, detect driving patterns, and identify aggressive driving behaviors. The system is based on neural networks trained on a comprehensive dataset of driving events, driving styles, and road conditions. The system effectively detects potential risks and helps mitigate the frequency and impact of accidents. The primary goal is to ensure the safety of drivers and vehicles. Collecting data involved gathering information on three key road events: normal street and normal drive, speed bumps, circular yellow speed bumps, and three aggressive driving actions: sudden start, sudden stop, and sudden entry. The gathered data is processed and analyzed using a machine learning system designed for limited power and memory devices. The developed system resulted in 91.9% accuracy, 93.6% precision, and 92% recall. The achieved inference time on an Arduino Nano 33 BLE Sense with a 32-bit CPU running at 64 MHz is 34 ms and requires 2.6 kB peak RAM and 139.9 kB program flash memory, making it suitable for resource-constrained embedded systems.
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024Sinan KOZAK
Sinan from the Delivery Hero mobile infrastructure engineering team shares a deep dive into performance acceleration with Gradle build cache optimizations. Sinan shares their journey into solving complex build-cache problems that affect Gradle builds. By understanding the challenges and solutions found in our journey, we aim to demonstrate the possibilities for faster builds. The case study reveals how overlapping outputs and cache misconfigurations led to significant increases in build times, especially as the project scaled up with numerous modules using Paparazzi tests. The journey from diagnosing to defeating cache issues offers invaluable lessons on maintaining cache integrity without sacrificing functionality.
AI assisted telemedicine KIOSK for Rural India.pptx
Skpl 5114100021 5114100110
1. SOFTWARE REQUIREMENT SPECIFICATION
DOCUMENT
DEPTCAL
(DEPARTMENT CALENDAR)
to:
Informatics Department
Sepuluh Nopember Institute of Technology
by:
Rina Wijaya Kusuma Wardhani 5114100021
Rafiar Rahmansyah 5114100110
Jurusan Teknik Informatika - Institut Teknologi Sepuluh Nopember
Kampus ITS KeputihSukolilo Surabaya
Informatics
Department ITS
Document Number Page
SRS-001 1/#52
Revisio
n
- DD MM YYYY
2. Informatics Department ITS SRS-001 Page 2 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
REVISION LIST
Revision Description
A
B
C
D
E
F
G
3. Informatics Department ITS SRS-001 Page 3 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
DATE
INDEX
- A B C D E F G
Written
by
Examined
by
Approved
by
4. Informatics Department ITS SRS-001 Page 4 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
Revision Page List
Page Revision Page Revision
5. Informatics Department ITS SRS-001 Page 5 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
Table of Content
1. Preface ................................................................................................................................9
1.1 Document Writing Purpose ...........................................................................................9
1.2 Problem Scope................................................................................................................9
1.3 Definition .......................................................................................................................9
1.4 Naming and Numbering Rule ......................................................................................10
1.5 References ...................................................................................................................10
1.6 Document Summary.....................................................................................................10
2. Software in General Description.....................................................................................11
2.1 General Description of System ....................................................................................11
2.2 Product Function .........................................................................................................11
2.3 User Characteristic ......................................................................................................11
2.4 Boundary ......................................................................................................................12
2.5 Operation Environment ...............................................................................................12
3. Requirement in General Description .............................................................................12
3.1 External Interface Requirement ...................................................................................12
3.1.1 User Interface ......................................................................................................12
3.1.2 Hardware Interface ..............................................................................................13
3.1.3 Software Interface................................................................................................13
3.1.4 Communication Interface ....................................................................................13
3.2 Function Description ...................................................................................................13
3.2.1 Use Case Diagram ...............................................................................................13
3.2.2 Function 1: View Calendar..................................................................................14
3.2.2.1 Scenario: View Calendar.........................................................................14
3.2.2.2 Activity Diagram: View Calendar...........................................................14
3.2.2.3 Sequence Diagram: View Calendar.........................................................15
3.2.2.4 Collaboration Diagram: View Calendar..................................................15
3.2.3 Function 2: View Agenda ...................................................................................16
3.2.3.1 Scenario: View Agenda...........................................................................16
3.2.3.2 Activity Diagram: View Agenda........................................................................ 16
3.2.3.3 Sequence Diagram: View Agenda...................................................................... 17
3.2.3.4 Collaboration Diagram: View Agenda.............................................................. 17
3.2.4 Function 3: View Detail Schedule ......................................................................18
3.2.4.1 Scenario: View Detail Schedule..............................................................18
3.2.4.2 Activity Diagram: View Detail Schedule ........................................................ 18
3.2.4.3 Sequence Diagram: View Detail Schedule ..................................................... 19
3.2.4.4 Collaboration Diagram: View Detail Schedule ............................................. 19
3.2.5 Function 4: Edit Schedule ...................................................................................20
6. Informatics Department ITS SRS-001 Page 6 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.5.1 Scenario: Edit Schedule......................................................................................... 20
3.2.5.2 Activity Diagram: Edit Schedule ....................................................................... 21
3.2.5.3 Sequence Diagram: Edit Schedule .................................................................... 22
3.2.5.4 Collaboration Diagram: Edit Schedule ............................................................ 23
3.2.6 Function 5: Delete Schedule ...............................................................................23
3.2.6.1 Scenario: Delete Schedule.................................................................................... 23
3.2.6.2 Activity Diagram: Delete Schedule .................................................................. 24
3.2.6.3 Sequence Diagram: Delete Schedule ................................................................ 25
3.2.6.4 Collaboration Diagram: Delete Schedule ........................................................ 26
3.2.7 Function 6: Create Schedule ...............................................................................26
3.2.7.1 Scenario: Create Schedule.................................................................................... 26
3.2.7.2 Activity Diagram: Create Schedule .................................................................. 27
3.2.7.3 Sequence Diagram: Create Schedule ................................................................ 28
3.2.7.4 Collaboration Diagram: Create Schedule ........................................................ 29
3.2.8 Function 7: Add Participant ................................................................................29
3.2.8.1 Scenario: Add Participant .................................................................................... 29
3.2.8.2 Activity Diagram: Add Participant .................................................................... 30
3.2.8.3 Sequence Diagram: Add Participant ................................................................. 31
3.2.8.4 Collaboration Diagram: Add Participant ......................................................... 32
3.2.9 Function 8: View Notification ............................................................................32
3.2.9.1 Scenario: View Notification ................................................................................ 32
3.2.9.2 Activity Diagram: View Notification ............................................................... 33
3.2.9.3 Sequence Diagram: View Notification ............................................................ 34
3.2.9.4 Collaboration Diagram: View Notification .................................................... 35
3.2.10 Function 9: Create User ...................................................................................35
3.2.10.1 Scenario: Create User ........................................................................................ 35
3.2.10.2 Activity Diagram: Create User ....................................................................... 37
3.2.10.3 Sequence Diagram: Create User ..................................................................... 38
3.2.10.4 Collaboration Diagram: Create User ............................................................. 39
3.3 Class Description..........................................................................................................40
3.3.1 Class Diagram .....................................................................................................40
3.3.2 Domain Issue Description ...................................................................................41
3.3.3 Control Class Description....................................................................................41
3.3.4 Entity Class Description......................................................................................42
3.3.5 Boundary Class Description................................................................................43
3.4 Data Flow Diagram .....................................................................................................45
3.5 Non Functional Requirement Description ...................................................................47
3.6 Design Boundary .........................................................................................................47
3.7 Requirement Summary ................................................................................................48
3.7.1 Functional Requirement Summary......................................................................48
3.7.2 Non Functional Requirement Summary .............................................................48
7. Informatics Department ITS SRS-001 Page 7 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
List of Table
Table 1. Naming and Numbering Rule ....................................................................................10
Table 2. User Characteristic ....................................................................................................12
Table 3. Domain Issue Description .........................................................................................41
Table 4. Controller Class Description .....................................................................................41
Table 5. Entity Class Description ............................................................................................42
Table 6. Boundary Class Description ......................................................................................43
Table 7. Non Functional Requirement Description .................................................................47
Table 8. Functional Requirement Summary ............................................................................48
Table 9. Non Functional Requirement Summary ....................................................................48
List of Figure
Figure 1. Use Case Diagram.....................................................................................................13
Figure 2. Activity Diagram: View Calendar ...........................................................................14
Figure 3. Sequence Diagram: View Calendar .........................................................................15
Figure 4. Collaboration Diagram: View Calendar ...................................................................15
Figure 5. Activity Diagram: View Agenda .............................................................................16
Figure 6. Sequence Diagram: View Agenda ...........................................................................17
Figure 7. Collaboration Diagram: View Agenda .....................................................................17
Figure 8. Activity Diagram: View Detail Schedule ................................................................18
Figure 9. Sequence Diagram: View Detail Schedule ..............................................................19
Figure 10. Collaboration Diagram: View Detail Schedule .....................................................19
Figure 11. Activity Diagram: Edit Schedule ...........................................................................21
Figure 12. Sequence Diagram: Edit Schedule .........................................................................22
Figure 13. Collaboration Diagram: Edit Schedule ..................................................................23
Figure 14. Activity Diagram: Delete Schedule .......................................................................24
Figure 15. Sequence Diagram: Delete Schedule .....................................................................25
Figure 16. Collaboration Diagram: Delete Schedule ...............................................................26
Figure 17. Activity Diagram: Create Schedule .......................................................................27
Figure 18. Sequence Diagram: Create Schedule .....................................................................28
Figure 19. Collaboration Diagram: Create Schedule ...............................................................29
Figure 20. Activity Diagram: Add Participant ........................................................................30
Figure 21. Sequence Diagram: Add Participant ......................................................................31
Figure 22. Collaboration Diagram: Add Participant ...............................................................32
Figure 23. Activity Diagram: View Notification ....................................................................33
Figure 24. Sequence Diagram: View Notification ..................................................................34
Figure 25. Collaboration Diagram: View Notification ............................................................35
Figure 26. Activity Diagram: Create User ..............................................................................37
8. Informatics Department ITS SRS-001 Page 8 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
Figure 27. Sequence Diagram: Create User ............................................................................38
Figure 28. Collaboration Diagram: Create User ......................................................................39
Figure 29. Class Diagram ........................................................................................................40
Figure 30. Physical Data Model ..............................................................................................42
Figure 31. Data Flow Diagram ................................................................................................45
9. Informatics Department ITS SRS-001 Page 9 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
1 Preface
1.1 Document Writing Purpose
This document is about Software Requirement Specification to the system of
DeptCal or Department Calendar at Informatics Department, Sepuluh Nopember
Institute of Technology. The purpose of this document is to give the explanation about
the result of the software that is about to develope. The information can be general to
detail and comprehensive description of the software.
This document will be used as the reference in the development process and the
evaluation from the beginning to the end of it. With this document, we hope that the
development process of the software will be directional and focused and also does not
inflict the ambiguity, especially to the developer.
1.2 Problem Scope
The software that is going to be built is the system of Department Calendar, which
is the software in the form of web that is used to give the lecturer and student the
information about their schedule or department’s schedule in Department of
Informatics. That system can do such:
1. Give the information about the schedule in 2 ways; calendar of the month and
ordering schedule
2. Manage the schedule created by the user
3. Provide the sharing schedule feature so the related users can have the same related
schedule
4. Give the notification or reminder to the user related to their schedule
With this application, we hope that the user, in this case are the lecturer and student
of informatics can be easily managing their schedule and always update to the
schedule of the department itself.
1.3 Definition
These are the list of important definitions that appear in this document:
SRS : Software Requirements Specification, or
SKPL : Spesifikasi Kebutuhan Perangkat Lunak
IEEE : Institute of Electrical and Electronics Engineering
The international standard to develop and design product.
ANSI : American National Standard Institute
American Standard Institution
TBD : To Be Defined
LAN : Local Area Network
10. Informatics Department ITS SRS-001 Page 10 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
1.4 Naming and Numbering Rule
This SRS Document writing uses several naming and numbering rules in some
different parts. Those naming and numbering rules are shown on the table 1 below.
Tabel 1. Naming and Numbering Rule
Part Naming/ Numbering Rule
Functional Requirement SKPL-FXX : Show the XX-th functional requirement
Non Functional
Requirement
SKPL-NFXX : Show the XX-th non functional requirement
Functional Requirement
Summary
SKPL-Fxxx where xxx is 3 digits integer starts from 000
Non Functional
Requirement Summary
SKPL-NFxxx where xxx is 3 digits integer starts from 000
1.5 References
These are the documents used as the references in the making of this SRS
document:
1) Software Requirement Spesification (SRS) – IEEE year 1999 by Karl E. Wiegers.
2) Panduan Penggunaan dan Pengisian Spesifikasi Perangkat Lunak (SKPL), Jurusan
Teknik Informatika, Institut Teknologi Sepuluh November.
3) Panduan Penggunaan dan Pengisian Spesifikasi Perangkat Lunak (SKPL), Jurusan
Teknik Informatika, Institut Teknologi Bandung.
1.6 Document Summary
This overall document consists of 3 chapter with the explanation as below:
● Chapter 1 Preface, is the introduction of this SRS document that consists of the
document writing purpose, problem scope, definition, naming and numbering
rules, references, and the general description of this document.
● Chapter 2 Software in General Description, define the software product
perspective and the assumption and dependency that are used on Department
Calendar System development.
● Chapter 3 Requirement in Detail Description, define the particular requirement to
Department Calendar System, which are the external interface requirement,
functional requirement, performance requirement, design boundary, software
system attribute, and the other requirement of Department Calendar System.
11. Informatics Department ITS SRS-001 Page 11 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
2 Software in General Description
2.1 General Description of System
DeptCal System is the system to give information about the schedule of
department and let the user to manage their own schedule related to the department
issue. DeptCal can give the view of schedules in 2 ways; calendar in a month and
ordering schedule. The user can also share their schedule to other user. There are 2
user types in DeptCal, such as general user which are lecturer, student, or
organization, and administrator of department. All of them can create their own
schedule and share it to the another related user. They also can see their schedule or
schedule that is shared to them. There is special case where department’s schedules
are shared automaticaly to other user so lecturer and student will always be up to date
to the department events.
DeptCal has some main parts based on the user, such as:
1. On general user’s side, the system provides the facilities such as the good views
to see the schedule through calendar view or agenda view, the easy way to create
a schedule and add the participant into it, and get the notification or reminder if
they have been added to someone’s schedule
2. On the administrator of department’s side, they can automatically share their
schedule to all of the user. It is because their schedules are usually about the
department events which are the main issues on this system purpose. They also
has special right to add/create another account of this system. It is used to
constraint the user which is informatics department people only.
DeptCal has also the protection and access right to the user due to the security and
the safety of the system.
2.2 Product Function
DeptCal software has some main functions, such as:
1. (SRS-F1) Can show the information about the schedule of the user and department
2. (SRS-F2) Can create a schedule on a date and describe it in detail about the title,
time, place, etc
3. (SRS-F3) Can edit the schedule that has been made
4. (SRS-F4) Can delete the schedule that has been made
5. (SRS-F5) Can add another user to the schedule so they can also see our schedule
6. (SRS-F6) Can get the notification about the shared schedule
7. (SRS-F7) Can create another account
2.3 User Characterisctic
The characteristics of the user from this system are explained on the table below:
12. Informatics Department ITS SRS-001 Page 12 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
Tabel 2. User Characteristic
No User Category Job Application Access
Right
Ability
1. General user Access the
system
Can see, create, edit
and delete schedule
1. Must be able to operate
the computer
2. Must be able to access
the internet and web
2. Department
administrator
Manage the
department
account
The schedule they
create is
automatically being
shared to all users
1. Must be able to operate
the computer
2. Must be able to access
the internet and web
Manage the
user of the
system
Can create another
account
2.4 Boundary
The development of DeptCal has boundaries, such as:
1. This system is made using HTML, PHP, and MySQL
2. The interface must be user friendly
3. The boundary from the hardware side, such as limited memory, limited storage,
the input must only be string or number
4. The other support system that is used are DBMS SQL-Server and PHPStorm
editor
5. The boundary of the user can only be added by the administrator of department
6. The user is part of informatics department only
7. The schedule content should be about the department issue.
2.5 Operation Environment
The specification of DeptCal:
Operating System Platform : Microsoft Windows
Operating System Version : Windows Server 2003/XP SP2/Vista/7/8
DBMS : SQL-Server
Job Frame : HTML, PHP, MySQL
3 Requirement in General Description
3.1 External Interface Requirement
3.1.1 User Interface
DeptCal uses Graphic User Interface. The user can do the input job using
the keyboard and mouse on Windows Operating System.
13. Informatics Department ITS SRS-001 Page 13 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.1.2 Hardware Interface
DeptCal system executes in the server computer. All of the computer that is
about to access the application must be connected to the internet.
3.1.3 Software Interface
DeptCal program will be built using HTML, PHP, MySQL language, SQL-
Server and Windows Operating System.
3.1.4 Communication Interface
DeptCal system is connected to the internet network so it can be accessed
anytime and anywhere.
3.2 Functional Description
3.2.1 Use Case Diagram
Figure 1. Use Case Diagram
DeptCal System
14. Informatics Department ITS SRS-001 Page 14 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.2 Function 1: View Calendar
3.2.2.1 Scenario: View Calendar
Use Case Code UC 001
Use Case Name View Calendar
Actor User
Description This use case describes how the user can see their
schedules (only title) in the form of calendar per month
Relation Generalization of View Schedule
Pre Condition User sees the schedule in the form of agenda
Post Condition There is a view of the schedules in the form of calendar
per month
Main Flow
Actor System
1 User select the view
calendar menu
2 System shows the schedule in the form of calendar per
month
Alternative Flow
-
Actor System
- -
3.2.2.2 Activity Diagram: View Calendar
15. Informatics Department ITS SRS-001 Page 15 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.2.3 Sequence Diagram: View Calendar
3.2.2.4 Collaboration Diagram: View Calendar
16. Informatics Department ITS SRS-001 Page 16 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.3 Function 2: View Agenda
3.2.3.1 Scenario: View Agenda
Use Case Code UC 002
Use Case Name View Agenda
Actor User
Description This use case describes how the user can see their
schedules (only title) in the form of chronological order
Relation Generalization of View Schedule
Pre Condition User sees the schedule in the form of calendar
Post Condition There is a view of the schedules in the form of
chronological order
Main Flow
Actor System
1. User select the view
agenda menu
2. System show the schedule in the form of chronological
order
Alternative Flow
-
Actor System
- -
3.2.3.2 Activity Diagram: View Agenda
17. Informatics Department ITS SRS-001 Page 17 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.3.3 Sequence Diagram: View Agenda
3.2.3.4 Collaboration Diagram: View Agenda
18. Informatics Department ITS SRS-001 Page 18 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.4 Function 3: View Detail Schedule
3.2.4.1 Scenario: View Detail Schedule
Use Case Code UC 003
Use Case Name View Detail Schedule
Actor User
Description This use case describes how the user can see the full detail
information of a schedule
Relation Extend of View Schedule
Pre Condition User sees all the schedule in the form of calendar or
agenda
Post Condition User sees the full detail information of a chosen schedule
Main Flow
Actor System
1. User select one of the
schedules
2. System shows the form of full detail information of the
selected schedule which are title, description, date, time,
place, and participant user
Alternative Flow
-
Actor System
- -
3.2.4.2 Activity Diagram: View Detail Schedule
19. Informatics Department ITS SRS-001 Page 19 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.4.3 Sequence Diagram: View Detail Schedule
3.2.4.4 Collaboration Diagram: View Detail Schedule
20. Informatics Department ITS SRS-001 Page 20 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.5 Function 4: Edit Schedule
3.2.5.1 Scenario: Edit Schedule
Use Case Code UC 004
Use Case Name Edit Schedule
Actor User
Description This use case describes how the user can edit their
schedule information
Relation Generalization of Manage Schedule
Pre Condition User sees the detail of the certain schedule
Post Condition The schedule is up to date
Main Flow
Actor System
1. User click the edit button
when user view the detail
of the certain schedule
3. User fill and edit the form
and click save button
2. System show the form of the schedule information to be
edited
4. System validate the input from user
A1. The input is invalid
5. System save the change and update the schedule
Alternative Flow
A1. The input is invalid
Actor System
A1.1 System give the warning
A1.2 Back to step 2
21. Informatics Department ITS SRS-001 Page 21 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.5.2 Activity Diagram: Edit Schedule
22. Informatics Department ITS SRS-001 Page 22 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.5.3 Sequence Diagram: Edit Schedule
23. Informatics Department ITS SRS-001 Page 23 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.5.4 Collaboration Diagram: Edit Schedule
3.2.6 Function 5: Delete Schedule
3.2.6.1 Scenario: Delete Schedule
Use Case Code UC 005
Use Case Name Delete Schedule
Actor User
Description This use case describes how the user can delete their
schedule
Relation Generalization of Manage Schedule
Pre Condition User sees the detail of the certain schedule
Post Condition The selected schedule will be deleted and user is back to
the view schedule page
Main Flow
Actor System
1. Click the delete button
when user view the detail
of the certain schedule
3. User click “yes”
A1. User Click “no”
2. System shows a warning to ensure the user
4. System delete the certain schedule
24. Informatics Department ITS SRS-001 Page 24 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
Alternative Flow
A1. User Click “no”
Actor System
A1.1 The system back to the view detail of the certain
schedule
3.2.6.2 Activity Diagram: Delete Schedule
25. Informatics Department ITS SRS-001 Page 25 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.6.3 Sequence Diagram: Delete Schedule
26. Informatics Department ITS SRS-001 Page 26 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.6.4 Collaboration Diagram: Delete Schedule
3.2.7 Function 6: Create Schedule
3.2.7.1 Scenario: Create Schedule
Use Case Code UC 006
Use Case Name Create Schedule
Actor User
Description This Use Case describes how the user can create a
schedule.
Relation Association with User
Pre Condition User view schedule as calendar or agenda
Post Condition User view schedule as calendar or agenda with a new
schedule in it
Main Flow
Actor System
1. User click the create
schedule button
3. User fill the form and
click save
2. System show the form of a schedule which contain title,
description, date, time, place, participant user
6. System validate the input from user
A1. The input is invalid
27. Informatics Department ITS SRS-001 Page 27 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
7. System add and save the schedule
Alternative Flow
A1. The input is invalid
Actor System
A1.1 System give the warning
A1.2 Back to step 2
3.2.7.2 Activity Diagram: Create Schedule
28. Informatics Department ITS SRS-001 Page 28 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.7.3 Sequence Diagram: Create Schedule
29. Informatics Department ITS SRS-001 Page 29 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.7.4 Collaboration Diagram: Create Schedule
3.2.8 Function 7: Add Participant
3.2.8.1 Scenario: Add Participant
Use Case Code UC 007
Use Case Name Add Participant
Actor User
Description This Use Case describes how the user can add the other
user as the participant of their schedule
Relation Include Relationship to Edit Schedule and Create
Schedule
Pre Condition User view edit or create scheudule form
Post Condition Participant in a certain schedule added
Main Flow
Actor System
1. User select add participant
button when create the
schedule or update the
schedule
30. Informatics Department ITS SRS-001 Page 30 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3. User type the other user’s
username and click add
2. System show the form to tag the other user into the
schedule
4. System check if the user have been added or there is no
user with such username
A1. The user with certain username doesn’t exist or the user
has been added
5. System save the participant
Alternative Flow
A1. The user with certain username doesn’t exist or the user have been added
Actor System
A1.1 System give the warning whether the username
doesn’t exist or the user has been added
A1.2 Back to step 2
3.2.8.2 Activity Diagram: Add Participant
31. Informatics Department ITS SRS-001 Page 31 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.8.3 Sequence Diagram: Add Participant
32. Informatics Department ITS SRS-001 Page 32 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.8.4 Collaboration Diagram: Add Participant
3.2.9 Function 8: View Notification
3.2.9.1 Scenario: View Notification
Use Case Code UC 008
Use Case Name View Notification
Actor User
Description This Use Case describes how the user can get and see the
notification if the other user add them into a schedule
Relation Association
Pre Condition User view schedule as calendar or agenda
Post Condition User view schedule as calendar or agenda with a certain
schedule being added
Main Flow
Actor System
1. User click the notification
menu
2. System give the information of any schedule that the
user have been added
Alternative Flow
-
33. Informatics Department ITS SRS-001 Page 33 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
Actor System
- -
3.2.9.2 Activity Diagram: View Notification
34. Informatics Department ITS SRS-001 Page 34 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.9.3 Sequence Diagram: View Notification
35. Informatics Department ITS SRS-001 Page 35 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.9.4 Collaboration Diagram: View Notification
3.2.10 Function 9: Create User
3.2.10.1 Scenario: Create User
Use Case Code UC 009
Use Case Name Create User
Actor Admin of Department
Description This Use Case describes how the admin of department can
create another account of organization, lecturer, and
student
Relation Association
Pre Condition There is no specific department calendar account of
organization, lecturer, or student
Post Condition There is specific department calendar account of
organization, lecturer, or student added to the application
Main Flow
Actor System
1 Admin of department user
select create user menu
36. Informatics Department ITS SRS-001 Page 36 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3 Admin department user
select user type;
organization, lecturer, or
student
5 Admin department user
fill the form and click
create
2 System give choice which user admin want to create,
organization, lecturer, or student
4 System show the form of the related user
6 System check the username
A1. The username already exist
7 System create and save the account as a new user with
certain username and the password will be the same as
the username
Alternative Flow
A1. User do not fill the required information
Actor System
A1.2 Admin of Department
User can’t create the account
A1.1 A1.1 System give the warning
37. Informatics Department ITS SRS-001 Page 37 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.10.2 Activity Diagram: Create User
38. Informatics Department ITS SRS-001 Page 38 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.10.3 Sequence Diagram: Create User
39. Informatics Department ITS SRS-001 Page 39 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.2.10.4 Collaboration Diagram: Create User
40. Informatics Department ITS SRS-001 Page 40 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.3 Class Description
3.3.1 Class Diagram
Figure 29. Class Diagram
41. Informatics Department ITS SRS-001 Page 41 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.3.2 Domain Issue Description
Table 3. Domain Issue Description
No
.
Nama
Metode Atribut Tugas
3.3.3 Control Class Description
Table 4. Control Class Description
No Nama Method Atributte Job
1 ScheduleControl
getSchedule()
Get all data
schedule from
ScheduleDB
getScheduleById()
Get data schedule
from ScheduleDB
by schedule_id
value
editDataSchedule()
Update data
schedule in
DBSchedule
checkInput()
Check the
completeness of
data input
createLog()
Create activity
log when create,
edit, or delete
schedule
deleteDataSchedule()
Delete data
schedule in
DBSchedule
createDataSchedule()
Create new data
schedule
2 ParticipantControl createDataParticipant()
Create new data
participant
3 NotificationControl getUserNotification()
Get data shared
schedule as the
notification
42. Informatics Department ITS SRS-001 Page 42 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
changeFlag()
Change the flag
of data participant
4 UserControl createDataUser()
Create new data
user
3.3.4 Entity Class Description (Persistent)
Figure 30. Physical Data Model
Table 5. Entity Class Description
No. Name Atributte Method Job
1. ScheduleDB
Schedule_id : integer
User_id: integer
Schedule_title: varchar
Schedule_description:
varchar
Schedule_date: date
Schedule_time: time
Schedule_place: varchar
selectData()
selectDataById()
insertData()
updateData()
deleteData()
Manage the
schedule like
create, edit, delete
and select the
data to be
displayed
43. Informatics Department ITS SRS-001 Page 43 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
2. ScheduleLogDB
Log_id: integer
Schedule_id: integer
Log_type_id: integer
Log_datetime: timestamp
insertData()
Add the log data
when do the
CRUD on the
DBSchedule
3. UserDB
User_ud: integer
Type_id: integer
User_username: varchar
User_password: varchar
User_name: varchar
checkUser()
insertData()
Select user data if
exist and add the
new user data
4. ParticipantDB
User_id: integer
Schedule_id: integer
Flag: integer
- insertData()
- selectData()
- updateData()
Add the data to
DBParticipant if
there is shared
schedule to other
user, select
schedule id by
user id, and
update the flag
data
3.3.5 Boundary Class Description
Table 6. Boundary Class Description
No. Name Method
Attri
bute
Job
1. ViewCalendarUI
chooseViewCalendar()
Choose the calendar
type of schedule as
view
showSchedulePerMont()
Display all schedule
based on the month
2. ViewAgendaUI
- chooseViewAgenda()
Choose the agenda type
of schedule as view
- showSchedule()
View all the schedules
ordered by time
3.
ViewDetailSchedule
UI
- chooseViewDetailSchedule()
Choose a schedule to
see its detail
information
- showDetailSchedule()
Display the detail
information of the
schedule
44. Informatics Department ITS SRS-001 Page 44 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
- chooseDeleteSchedule()
Choose a schedule to
be deleted
- showWarningDelete()
Give warning to ensure
the delete process
4. EditScheduleUI
chooseEditSchedule()
Choose to update the
certain schedule
showEditScheduleForm()
View the form of
updating schedule
- fillForm() Fill the form
- showWarning()
Give warning if the
input data is not valid
5. CreateScheduleUI
chooseCreateSchedule()
Choose to create a new
schedule
showCreateScheduleForm()
View the form of
creating schedule
fillForm() Fill the form
showWarning()
Give warning if the
input data is not valid
6. AddParticipantUI
chooseAddParticipant()
Choose to add the new
participant of schedule
showParticipantForm()
View the form of
adding participant
fillForm() Fill the form
showWarning()
Show warning if the
user is not exist
7. ViewNotificationUI
chooseShowNotification()
Choose to see
notfication
showNotification() View the notification
8. CreateUserUI
chooseCreateUser()
Choose to create a new
user
showUserType()
View the option to
create a certain user
chooseUserType()
Choose the user type to
be added
showInsertUserForm()
View the form of
creating a new user
fillForm() Fill the form
showWarning()
Give warning if the
user is already exist
45. Informatics Department ITS SRS-001 Page 45 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.4 Data Flow Diagram
Data Flow Diagram level 0
46. Informatics Department ITS SRS-001 Page 46 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
Data Flow Diagram level 1
Figure 31. Data Flow Diagram
47. Informatics Department ITS SRS-001 Page 47 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.5 Non Functional Requirement Description
Table 7. Non Functional Requirement Description
SRS-Id Parameter Requirement
SRS-N01 Availability
This application must be able to operate in 24
hour, because it is used to manage schedule
in the various time based on the user, so the
user can use the application whenever they
want. This application must also be able to
log the user in, on several devices in the same
time.
SRS-N02 Reliability
This application must be built with the high
reliability. The failure to be tolerated must be
about 10%. The reliability must be also on
the telecommunication network to access the
internet. With those, we hope this application
can be used greatly whenever the user need
this.
SRS-N03 Ergonomy
This application must have the high value of
ergonomy or the comfortableness to the user.
This application will be built with the user
interface that easy to understand, nice view,
consistent, easy to be operated, and isn’t
confusing.
SRS-N04 Portability This application is not portable
SRS-N05 Memory
This application can accommodate the
database up to 160GB maximum.
SRS-N06 Response time
This application must be able to access the
database in 10 seconds.
SRS-N07 Safety This application network consists of firewall
SRS-N08 Security
This application has the access right to each
user and the password will be encrypted.
SRS-N09
Communication
Language
This application uses Bahasa as the
communication language
3.6 Design Boundary
a. Compatible to all type of HTML
48. Informatics Department ITS SRS-001 Page 48 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
3.7 Requirement Summary
3.7.1 Functional Requirement Summary
Table 8. Functional Requirement Summary
SRS-Id Explanation
SRS-F000 The system can let the user to log in to the application with their id and
password
SRS-F001 The system can show the schedule information in a view of a month or
agenda
SRS-F002 The system can let the user to create a schedule with the data requirement of
schedule title, schedule time, and description about it on a date
SRS-F003 The system can let the user to edit a schedule
SRS-F004 The system can let the user to delete a schedule
SRS-F005 The system can let the user to add another related user into a their schedule
SRS-F006 The system can give a notification if they are added by another user into their
schedule
SRS-F007 The system can let the specific user to create new account
SRS-F008 The system can store schedule data
SRS-F009 The system can store user data
SRS-F0010 The system can store some related users data with their schedule data
SRS-F0011 The system can record the activity of user as log data
3.7.2 Non Functional Requirement Summary
Table 9. Non Functional Requirement Summary
SRS-Id Explanation
SRS-NF001 The system is compatible to all type of browser
SRS-NF002 The system can operate on pc or mobile device.
SRS-NF003
There are 2 type of user based on the functionality of the application
such as general user and administrator of department. The general user
can be student, lecturer, or even student organization
SRS-NF004
The lecturer account have an id according to their lecturer code and
student account have an id according to their NRP
SRS-NF005
The lecturer and student account have been added into the application
by the administrator of department
SRS-NF006
Only administrator of department can create new account of the
application
SRS-NF007 The system can avoid the user to access another user's account
49. Informatics Department ITS SRS-001 Page 49 of 49
This document template and its information belongs to Software Engineering Laboratorium of Informatics Department-ITS and
is confidential. It is forbidden to make any copy without permission of Software Engineering Laboratorium of Informatics
Department-ITS.
SRS-NF008
The system can limit the user that the user can only edit and delete their
own schedule
SRS-NF009
The schedule made by department account can be seen by all general
user