The document provides a software design description for the SCC Newscast System. It describes the system architecture through module, process, and data decomposition. Key elements include administrator and user modules for authentication and announcement management, processes for registration and request verification, and data entities linking the modules and processes. Dependency relationships between modules, processes, and data are also specified through diagrams. The interface and detailed design depict how users will interact with the system and how modules are structured.
Software Project Management: Software Requirement SpecificationMinhas Kamal
Software Project Management: ResearchColab- Software Requirement Specification (Document-5)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
Software Project Management: Software Requirement SpecificationMinhas Kamal
Software Project Management: ResearchColab- Software Requirement Specification (Document-5)
Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).
ANALYZABILITY METRIC FOR MAINTAINABILITY OF OBJECT ORIENTED SOFTWARE SYSTEMIAEME Publication
Analyzability is one of the major factors in the prediction of maintainability aspect that can improve the quality of the intended software solution in an appropriate manner. In fact, the right analyzability measure will go a long way in decreasing the inadequacies and deficiencies through identification of the modified parts and failure causes in the software system. The analyzability metric identification is not possible in every software solution because of its non- functional nature in the real world, but in object-oriented software system there is an opportunity to find out the analyzability metric in the form of class inheritance hierarchies. In this research paper, the researcher measured the analyzability factor for the object-oriented software systems and also validated in accordance with the famed weyker’s properties. The proposed analyzability metric here is intended to lead the new developments in object-oriented software maintainability parameter in future and help the new researchers do their research the right way thus eventually achieving the quality aspect of the objectoriented software system and fulfilling the needs of the users.
The Operating System acts as a platform of information exchange between your computer's
hardware and the applications running on it. Most people are familiar with the Windows
Operating System family (like Windows 10, XP, or Vista) or Apple's suite of Operating Systems
(like Catalina, Mojave, or Sierra)
Personalization of Field,Form Personalization,Field Hiding,Making Field as Required,Oracle HRMS,oracle,When-New-Form-Instance,Functions,ora17hr,oraclehrms,hrms,oracle hrms functional setup
ANALYZABILITY METRIC FOR MAINTAINABILITY OF OBJECT ORIENTED SOFTWARE SYSTEMIAEME Publication
Analyzability is one of the major factors in the prediction of maintainability aspect that can improve the quality of the intended software solution in an appropriate manner. In fact, the right analyzability measure will go a long way in decreasing the inadequacies and deficiencies through identification of the modified parts and failure causes in the software system. The analyzability metric identification is not possible in every software solution because of its non- functional nature in the real world, but in object-oriented software system there is an opportunity to find out the analyzability metric in the form of class inheritance hierarchies. In this research paper, the researcher measured the analyzability factor for the object-oriented software systems and also validated in accordance with the famed weyker’s properties. The proposed analyzability metric here is intended to lead the new developments in object-oriented software maintainability parameter in future and help the new researchers do their research the right way thus eventually achieving the quality aspect of the objectoriented software system and fulfilling the needs of the users.
The Operating System acts as a platform of information exchange between your computer's
hardware and the applications running on it. Most people are familiar with the Windows
Operating System family (like Windows 10, XP, or Vista) or Apple's suite of Operating Systems
(like Catalina, Mojave, or Sierra)
Personalization of Field,Form Personalization,Field Hiding,Making Field as Required,Oracle HRMS,oracle,When-New-Form-Instance,Functions,ora17hr,oraclehrms,hrms,oracle hrms functional setup
Part 1 Major Events DocumentationScenario You visit a retail.docxalisondakintxt
Part 1: Major Events Documentation
Scenario: You visit a retail establishment, shop around, and finally carry several products to one of the point of sale (POS) terminals distributed openly around the store. You produce a credit card, the salesclerk processes the transaction, bags your goods, and hands you the receipt. On your way to the exit, a store employee asks to see your receipt and checks the contents of the store bag. Document each of the major events just described and explain them in terms of the PCI compliance standard. Include this report in your assignment.
Part 2: PCI Compliance
This part of the assignment will cover PCI. Please refer to the attached file in your responses.
Respond to and address the following in essay style:
1. Suppose HGA’s mainframe, depicted in Figure B-1, stored cardholder data in the private databases. What steps should be taken to protect that data in order to be PCI compliant?
2. HGA’s mainframe has network connectivity. Assuming that cardholder data is transmitted across these networks, describe how data should be protected in transmission.
3. Users are located at various sites connected to the HGA network. Suggest appropriate access controls to restrict unauthorized users from looking at cardholder data.
4. The PCI specification notes that all systems and network devices connected to a system that stores, transmits, or processes cardholder data is in scope and must comply with PCI specifications. To avoid having the whole network subject to PCI specifications, how would you segment the network to reduce the scope of compliance?
Assignment Requirements:
Submit your assignment in the usual double-spaced APA-styled report. At least four pages of material are expected beyond the title page, table of contents, abstract, and references page.
· Answers contain sufficient information to adequately answer the questions
· No spelling errors
· No grammar errors
CRSS Network Diagram
Copyright Rasmussen, Inc. 2013. Proprietary and Confidential.
1
1
image3.png
image5.png
FedRAMP Security Assessment Plan (SAP)
Third Party Assessment
Prepared by
<Your Name>
for
Country Roads Space Systems
&
NASA
CRSS Information Systems. Administration and Classified Networks
Version #.#
<DATE>
MOCK Plan
CRSS Information Systems. Administration and Classified Networks | Version #.# Date
Controlled Unclassified Information Page | 10
System Assessment Plan
Prepared by
Identification of Organization that Prepared this Document
Student NameEnter Your Name
Rasmussen Email AddressEnter Rasmussen Email Address
ClassEnter Class Name
Course and SemesterEnter Section Number and Semester
Prepared for
Identification of Cloud Service Provider
Organization NameNASA
Street Address300 E St. SW
Suite/Room/BuildingIA Office Floor 2
City, State ZipWashington DC 20546
Revision History
Date
Description
Version of SSP
Author<Date><Revision Description><Version><Author><Date><Revision Description><Versi.
1RUNNING HEAD Normalization2NormalizationNORM.docxdrennanmicah
1
RUNNING HEAD: Normalization
2
Normalization
NORMALIZATION
Charles Williams
CS352 Unit 3 IP
Professor Jeffery Karlberg
1/26/2019
Table of Contents
Table of Contents………………………………………………………………………………………………………………………………………………………………………………………………..….2
The Database Models, Languages, and Architecture 3
Database System Development Life Cycle 5
Database Management Systems 6
Advanced SQL 11
Web and Data Warehousing and Mining in the Business World 12
References 13
Database management
It is important that a formal design methodology is used as it provides a mathematical approach to coming up with a reliable database that consolidates all the environments that use the database. A design methodology helps as it provides a way in which the whole designing and development can be done with minimum errors. The design methodology helps in identifying the requirements, the specifications and design levels of the database and data warehouse up for development. The planning stage of the consolidated data base is very important as it involves the coming up with plans that will guide the development of the database (Mabogunje, 2015). The plans help in managing quality, time, risks and other related issues that might affect the design and development of the database and eventually the data warehouse.
The three layers of the 3-level ANSI-SPARC architecture include; a physical schema which is responsible for defining how data is to be stored, a conceptual schema which is responsible for indexing and relating data, and the external schema which is responsible for showing how information was presented. The 3-level ANSI-SPARC type of architecture is designed to guard and guide data change. The primary function of the first layer is to define how data is stored. It is important to note that there can be changes in the physical schema and the changes will not affect how external applications will interact with the stored data (Pokorný, 2018). The second layer’s primary function is to provide a consolidated view of a database. The third layer’s primary function is to define richer APIs and it can do so without necessarily having to change the underlying storage mechanisms in place. The 3-level ANSI-SPARC architecture helps in promoting data independence which in turn helps save time in the long run through the conceptual schema which emphasizes data mapping.
Data administrator and database administrator
A data administrator is an individual whose function is to gather data requirements, analyze data as well as design data and classify data types. They two primary roles of a data administrator include; coming up with data standards that will be applied in databases, and coming up with policies that will dictate on data security, data access, data usage, dataflow well as data authorization in an organization. Other minor duties of data administrator include; playing an assistance role by coming up with data resources and allowing for the sharing of data across ap.
MEDICAL FACILITY ANALYSIS2MEDICAL FACILITY ANALYSIS16.docxARIV4
MEDICAL FACILITY ANALYSIS 2
MEDICAL FACILITY ANALYSIS 16
Medical Facility Analysis
Connie Farris
Colorado Technical University
Information Technology Architectures
(IT401-1801B-02)
Jennifer Merritt
Running head: MEDICAL FACILTY ANALYSIS 1
Table of Contents
Project Outline………………………………………………………………………...3
System Requirements …………………………………………………………………3
Architecture Selection………………………………………………………………….6
Resources and Timeline……………………………………………………………….8
Security…………………………………………………………………………………11
Final Analysis and Recommendations………………………………………………….13
References……………………………………………………………………………….15
Project Outline
Health care delivery systems are complex sociotechnical systems, characterized by dynamic interchanges with their environments (e.g., markets, payers, regulators, and consumers) and interactions among internal system components. These components include people, physical settings, technologies, care processes, and organization (e.g., rules, structure, information systems, communication, rewards, work flow, culture). ("Agency for Healthcare Research and Quality,", 2012) A local medical facility has requested an analysis to determine what will be required to update the current system and include video consults for the patients. This company has locations in 7 states of the southeastern part of the US. The process will be implemented at 21 locations. Over the next few weeks I will research the details which will include software, hardware, cost for equipment upgrades, and other extra cost that may be involved according to system requirements listed below. Network configuration will be discussed in the functions of the system. The need for the time frame for the project will also be considered. The main concern is to deliver a quality system. The final product will include a system where patients will be able to have face to face consultations with the doctor or PA through video capability.
System Requirements
. The first step is that the operating systems be updated with Microsoft 64 or 32-bit Windows 10 Pro, Windows 8 Pro, or Windows 7 Professional for best performance. Systems utilizing the architecture will have processors that are Intel Core i5-3470 3.2GHz LGA 1155 77W Quad-Core Desktop Processor equivalent or higher. The architecture requires 6 GB DDR3 RAM for memory and 250 GB of free space or higher for the hard drive. Uninterruptible Power Supply (UPS) is required for the client’s Information Technology (IT) professional to install. The HP LaserJet 3000 or 4000 Series printers are recommended. Broadband internet connections (specifically Cable) are recommended. For the 21 locations Logitech Meetup 4K HD Video Conference Camera with Integrated Audio will be purchased and installed. ("Hardware Specifications - American Medical Software", 2018)
The Functions of the System
The functions of this system will be to perform the basic functions of any medical offices. The system will be able to book appoint ...
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
1. SAINT COLUMBAN COLLEGE
PAGADIAN CITY
COLLEGE OF COMPUTER STUDIES
Software Design Description
for
SCC Newscast System
IT Group 2
“Mach5”
Almonte, Jelly Mae P.
Baltazar, Jessaneth B.
Ching Carl Angelo L.
Ihara Jr, Noel B.
Salazar, Ragde Ama T.
2. Signature
The following signature indicates approval of the enclosed Software Requirements Specifications Document.
Noel B. Ihara, Jr.
Project manager
Jelly Mae P. Almonte Carl Angelo L. Ching
System Analyst Programmer
Ragde Ama T. Salazar Jessaneth B. Baltazar
Quality Assurance Documenter
Mr. Neil Owen B. Jandugan
Adviser/Editor
Submitted and accepted by:
Mr. Philipcris C. Encarnacion, MCS
CCS Dean
3. Change History
Table 1
Revisions Date Reason For Changes Person who
suggested the
changes
Group Name June 16, 2014 Team Celeron change its name to
Mach5 because the meaning of
Celeron itself does not suit the group’s
characteristics.
Jessaneth B. Baltazar
(Documenter)
Title Name September 8,2014 The title of the study was changed
from E-Bulletin to SCC Newscast
System to make it more suitable with
the proposed system.
Ragde Ama T. Salazar
(QA Tester)
List of Figures October 24, 2014 The list of figures was revised and the
alignment of the content was properly
arranged.
Jessaneth B. Baltazar
(Documenter)
List of Table October 24, 2014 The page number of the list of tables
was changed.
Jessaneth B. Baltazar
(Documenter)
4. Preface
This document contains the software design descriptions of SCC Newscast System. This document is prepared
according to the “IEEE Standard for Information Technology Software Design Descriptions – IEEE Std 1016 -
2009” document. This Software Design Documentation (SDD) provides a complete description of all the system
design and views of the SCC Newscast System. The first and second sections of this document include the
purpose, scope, definitions of the document and the references used though out the document. The third
section includes the decomposition description for software design descriptions. The fourth section contains
dependency description information content, the fifth section includes the interface description and lastly, the
sixth section presents the detailed design of the SCC Newscast System. The main aim of SDD is to give
information’s to clients about the processes of the system. This document is very useful in Software Test Design
(STD) in conducting test of the system.
5. Table of Contents
Signature....................................................................................................................................................................................2
Change History..........................................................................................................................................................................3
Preface........................................................................................................................................................................................4
Table of Contents.......................................................................................................................................................................5
List of Figures............................................................................................................................................................................6
List of Table................................................................................................................................................................................7
1. Introduction...........................................................................................................................................................................8
1.1. Purpose.............................................................................................................................................................................................8
1.2. Scope................................................................................................................................................................................................8
1.3. Definitions and Acronyms................................................................................................................................................................8
2. References..............................................................................................................................................................................9
3. Decomposition Description.................................................................................................................................................10
3.1. Module Decomposition..................................................................................................................................................................10
3.1.1. Administrator Class Description...........................................................................................................................................10
3.2. Concurrent Process Decomposition................................................................................................................................................10
3.2.1. Registration Process Description..........................................................................................................................................10
3.2.2. Request Verification Process Description..............................................................................................................................10
3.3. Data Decomposition.......................................................................................................................................................................10
3.3.1. Data Entity Admin Description.............................................................................................................................................10
3.3.2. Data Entity User Description................................................................................................................................................11
4. Dependency Description ....................................................................................................................................................12
4.1. Inter-module Dependencies............................................................................................................................................................12
4.2. Inter-process Dependencies............................................................................................................................................................12
4.3. Data Dependencies.........................................................................................................................................................................13
5. Interface Description...........................................................................................................................................................14
5.1. Module Interface ...........................................................................................................................................................................14
5.1.1. Module 1: Log-in Form.........................................................................................................................................................14
5.1.2. Module 2: Main Form...........................................................................................................................................................15
5.1.3. Module 3: Announcement Management Form......................................................................................................................16
5.1.4. Module 4: Sample Output.....................................................................................................................................................17
5.1.5. Module 5: Templates.............................................................................................................................................................18
5.2. Process Interface ............................................................................................................................................................................19
5.2.1. Adding of announcement in a form of a video/text format.....................................................................................................19
6. Detailed Design....................................................................................................................................................................20
6.1. Module Detailed Design ................................................................................................................................................................20
6.1.1. Module Detail.......................................................................................................................................................................20
7. Appendices...........................................................................................................................................................................21
7.1. Use case realization (Sequence diagram / Communication diagram)..............................................................................................21
7.2. Entity-relationship diagram............................................................................................................................................................22
8. Index.....................................................................................................................................................................................23
6. List of Figures
Figure 1: Module Log-in Form ...............................................................................................................................12
Figure 2: Main Form ……………………………….………………………………………………………………............13
Figure 3: Announcement Management Form ………………..…………………………...………………………….….13
Figure 4: Sample Output ………………………………………..…...………………………………...……..……………14
Figure 6: Templates…………………….……..………………………………….…………………………………………14
Figure 7: Adding of announcement in a form of a video/text format …………………….........................................32
Figure 8: UML Activity Diagram …………………………………..…..………...………….…………….……………….16
Figure 9: Input-Process-Output Diagram …………………………..….……………………….…………………….….19
Figure 10: Class Diagram…………………………………………………………………………………………………..20
Figure 11: Sequence Diagram…………………………………………………………………………………………….21
Figure 12: User Interface Design………………………………………………………………………………...……22-24
Figure 13: Entity-Relationship Diagram…………………………………………………………………………………..25
7. List of Table
Table 1: Change History…………………………………………………………………………………...…………………..3
Table 2: Definitions and Acronyms……………………………………………………………………................................8
8. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
1. Introduction
Software Design Description introduced in this document describes the whole description of the system together
with its modules, data decomposition and class diagram in order to meet and accomplished all requirements that
are needed to complete and finish the whole system.
1.1. Purpose
The purpose of this study is to enable the optimum use of the system in disseminating information to the SCCians
through submission and approval of request to the Information Office by the aid of multimedia and networking
technology. The purpose of this software design description (SDD) document is to describe how the software will
be structured to satisfy the requirements of the SCC Newscast System. This document will explain the design
details of the system.
1.2. Scope
This document contains a description and scope of the objective and benefits of SCC Newscast System. The
basic architecture is a client/server or a windows form application that connects the three departments to the
Information office. It will be more efficient if the three departments will only send the announcement virtually. The
basic pages contain functions related to the current form. The administrator is in charge of the system, shall have
full access to the database and is authorized to make changes if it is considered to be necessary.
1.3. Definitions and Acronyms
Table 2
Term Definition
SDD Software design description to specify
system architecture and system design.
Database Collection of all the information monitored by
this system.
Design A document that shows the architecture of
the system and the assignment of its
component to physical nodes.
Module A group of related activities.
Page 8 of 23
9. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
2. References
• [IEEE] Recommended Practice for Software Design Descriptions in “IEEE Standards Collection,”
1998 edition.
• https://www.google.com.ph/#q=software+design+description+sample
• https://www.google.com.ph/url?
sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0CCcQFjAC&url=https%3A%2F
%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F24846%2FExample-
SoftwareDesignDocument-
LegalXMLUtility.pdf&ei=nhpPVP_VGcHf8AXYnoGwBg&usg=AFQjCNGogpXu90mB2JagXPOgEAhgkqIhL
Q&bvm=bv.77880786,d.dGY
Page 9 of 23
10. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
3. Decomposition Description
This section of this document decomposes each use-case feature into its data flow processes by examining its
data flow diagram and its process flow through the use of sequence diagrams. These assist us in determining the
preliminary members and methods of the modules that need to be implemented, or the modifications to existing
modules to implement the feature. This document uses the names of the use cases in the Software Requirement
Specification document as the names of the features. This section includes the description of the intended design
to meet the requirements. When appropriate, the use cases will be expanded to include system requirements. This
section also incorporates a number of sequence diagrams, updated from the initial prototype and analysis.
3.1. Module Decomposition
Module Decomposition is a decomposition of a graph into subsets of vertices called modules.
3.1.1. Administrator Class Description
This class includes the attributes of the administrator which specifies the author, department type, timeframe,
announcement details. It also identifies the previous announcement proposal by displaying the time, date, author
name and department type. This class is design for verifying the pending announcement proposal and finalizing
information for the proposed announcement.
3.2. Concurrent Process Decomposition
3.2.1. Registration Process Description
This process dictates the functionality of the system because this is where the user of the system are registered in
order to have their account relevant to perform the rest of the operations included in the system. This also creates
an event for the user specifying which department they belong.
Only the admin can create a guest or another account to be used by the information personnel. It will only require
a username and a password to fill it up.
3.2.2. Request Verification Process Description
This process is to be performed by the Information personnel by means of logging in to the admin workstation to
gain access to the admin panel and check the notification displayed in the system tray in order to view the recent
proposed announcement/news whether it is to be approved or not. If the Information personnel will approve a
particular announcement, it will then be automatically queued to the playlist and if the proposed announcement is
disapprove it will be deleted in the pending announcement list.. There will be notifications if there are queued
announcements on the database.
3.3. Data Decomposition
3.3.1. Data Entity Admin Description
This entity will do the process of request verification process and for most of the accessibility as for maintaining
the system’s database content. This entity will do the process of registering the new users, verify the user’s
account and have the capability of maintaining the database of the system.
Page 10 of 23
11. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
3.3.2. Data Entity User Description
This entity will do the processes ranging from sending an approval of announcement entry, filling up the pending
list and updating the admin’s activity log.
Page 11 of 23
12. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
4. Dependency Description
4.1. Inter-module Dependencies
When designing an Inter-module Dependencies of the system, it could be designed by two broad ways and the
first way is to design the complete system using the known existing system and implement new features needed to
enhance the effectiveness of the system and test it in the real conditions. An alternative way would be to design
the system and usually due to the cost of putting up interfaces between modules.
The module of the SCC Newscast System depends in the dissemination of information. This inter-module of the
study is the display of the announcements and it includes the database of the system. Then the entire information
that has been entered will be saved in the database, which is from the announcement input process until
displaying it to other monitor.
4.2. Inter-process Dependencies
The inter process of posting an announcement will be based on the user’s process which is filling up the
announcement information provided in order to submit a proposal and then it will be added to the list of pending
announcements.
Figure 1
Figure 1 provides an overview of the system by describing the objects and classes inside the system and the
relationships between them.
Page 12 of 23
13. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
4.3. Data Dependencies
Data Dependencies are based on the user. They are the one who will verify or approve the queued
announcement.
Page 13 of 23
14. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
5. Interface Description
…
5.1. Module Interface
…
5.1.1. Module 1: Log-in Form
Figure 2
Figure 2 shows the user authentication form which requires username and password to gain access to the main
form.
Page 14 of 23
15. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
5.1.2. Module 2: Main Form
Figure 3
Figure 3 shows the main form of the admin panel side which is capable of managing event, choosing template
and notification section.
Page 15 of 23
16. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
5.1.3. Module 3: Announcement Management Form
Figure 4
This figure 4 shows the Announcement Management Form which allows the user to update display, search, add,
delete and update running text.
Page 16 of 23
17. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
5.1.4. Module 4: Sample Output
Figure 5
Figure 5 shows the output form. This is the output screen which will be displayed in the four (4) monitor inside
Saint Columban College.
Page 17 of 23
18. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
5.1.5. Module 5: Templates
Figure 6
Figure 6 shows the template form which allows the user to choose desired template for the specific
announcement.
Page 18 of 23
19. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
5.2. Process Interface
…
5.2.1. Adding of announcement in a form of a video/text format
Figure 7
Figure 7 shows the adding of announcement where the user can either add a video, input announcement or add
a running text.
Page 19 of 23
20. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
6. Detailed Design
…
6.1. Module Detailed Design
…
6.1.1. Module Detail
The Main Form is the control for managing the announcements. The second display or the extended display is
responsible for showing the announcements on the monitors.
Figure 8
Figure shows the Activity between the Departments, Admin and The System.
Page 20 of 23
21. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
7. Appendices
….
7.1. Use case realization (Sequence diagram / Communication diagram)
Figure 9
The figure above shows the sequence of the processes happen in the SCC Newscast System.
Page 21 of 23
22. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
7.2. Entity-relationship diagram
Figure 10
This figure above shows the entity relationship diagram of the system. It explained how the different tables in the
database connected with the other tables.
Page 22 of 23
23. Software Design Description
SCC Newscast System
Document Version: 3.0
Published Date: 27 October 2014
8. Index
Attributes 12,
Data Entity 13, 16
References 11
Software Design 9,11
Page 23 of 23