mirror of
https://github.com/andatoshiki/toshiki-notebook.git
synced 2026-06-06 00:46:29 +00:00
doc(cis105): add lectrure notes for chapter 15 and 16 centralizing with it careers and business systems including schedules for final week & add correlated sidebar hyperlink entry components for two affiliated note pages
This commit is contained in:
parent
30eecb1c19
commit
37c8f26eb8
@ -229,6 +229,14 @@ export const sidebar: DefaultTheme.Config['sidebar'] = {
|
|||||||
{
|
{
|
||||||
text: 'Lect 14: More SQL Statements',
|
text: 'Lect 14: More SQL Statements',
|
||||||
link: '/academic/cis105/cis105-l14-lecture-note'
|
link: '/academic/cis105/cis105-l14-lecture-note'
|
||||||
|
},
|
||||||
|
{
|
||||||
|
text: 'Lect 15: Business System Reporting',
|
||||||
|
link: '/academic/cis105/cis105-l15-lecture-note'
|
||||||
|
},
|
||||||
|
{
|
||||||
|
text: 'Lect 16: Information Technology Careers',
|
||||||
|
link: '/academic/cis105/cis105-l16-lecture-note'
|
||||||
}
|
}
|
||||||
],
|
],
|
||||||
},
|
},
|
||||||
|
|||||||
41
docs/academic/cis105/cis105-l15-lecture-note.md
Normal file
41
docs/academic/cis105/cis105-l15-lecture-note.md
Normal file
@ -0,0 +1,41 @@
|
|||||||
|
# CIS105: Computer Applications & Information Systems Lect. 15
|
||||||
|
|
||||||
|
## Chapter 15: Business System Reporting
|
||||||
|
|
||||||
|
> **Final months schedule**
|
||||||
|
>
|
||||||
|
> - Today 4/9: Chapter 15/16
|
||||||
|
> - Thursday 4/11: Final SQL Assessment
|
||||||
|
> - Tuesday 4/16; Final Lecture and Final Exam Review
|
||||||
|
> - Thursday 4/18: MKT
|
||||||
|
> - 4/23 & 4/26: Zoom Office Hours
|
||||||
|
> - Final Exam: 4/25 - 4/26
|
||||||
|
> - Final day to complete all missing assignments: 4/28
|
||||||
|
|
||||||
|
### 15.1: Business System Reporting
|
||||||
|
|
||||||
|
- Defined as informaitonal output from an information system to facilitate decision-making.
|
||||||
|
- Report are periodic in nature
|
||||||
|
- Daily, weekly, monthly, etc
|
||||||
|
- Demand / Ad Hoc Reports
|
||||||
|
- Strategic vs. Tactical decisions
|
||||||
|
- Three main aspects of reporting:
|
||||||
|
- Reporting summarization levels
|
||||||
|
- Analysis and predictive reporting
|
||||||
|
- Management Level Reporting
|
||||||
|
- Reporting Summarization Levels: The level of detail or summarization in the report
|
||||||
|
- Transaction Processing System (TPS)
|
||||||
|
- Uses databases to store data
|
||||||
|
- Groundwork for all other reports
|
||||||
|
- Highest level of detail
|
||||||
|
- Analysis and Predictive Reporting
|
||||||
|
- Use TPS as a foundation
|
||||||
|
- Trend reporting
|
||||||
|
- Graphical repors
|
||||||
|
- Budget, forecast, and variance reports
|
||||||
|
- Management Level reporting
|
||||||
|
- Top-level executive reporting
|
||||||
|
- Management reporting
|
||||||
|
- Supervisory reporting
|
||||||
|
|
||||||
|
#
|
||||||
79
docs/academic/cis105/cis105-l16-lecture-note.md
Normal file
79
docs/academic/cis105/cis105-l16-lecture-note.md
Normal file
@ -0,0 +1,79 @@
|
|||||||
|
# CIS105: Computer Applications & Information Systems Lect. 16
|
||||||
|
|
||||||
|
## Chapter 16: Information Technology Careers
|
||||||
|
|
||||||
|
### 16.1: IT Careers Intro
|
||||||
|
|
||||||
|
- Information Technology (IT) is everywhere
|
||||||
|
- A common axiom for IT professionals is "know the business"
|
||||||
|
- **Value-Added**: Refers to the added value of a product or service over the cost of products and services.
|
||||||
|
|
||||||
|
### 16.2: Business IT Perception
|
||||||
|
|
||||||
|
- IT department are responsible for servicing and enhancing all computing, technical assets, and intellectual property of a business organization
|
||||||
|
- Service IT
|
||||||
|
- IT consulting
|
||||||
|
- IT is the glue that holds organizations together
|
||||||
|
|
||||||
|
### 16.3: Information Technology Jobs
|
||||||
|
|
||||||
|
- **Chief Information Officer (CIO)**: Te board-level head of Information Technology departments
|
||||||
|
- AKA Chief Technology Officer (CTO)
|
||||||
|
- Replaced 'IT Director' title
|
||||||
|
- Highest paid technology position
|
||||||
|
- Head Application Developers In charge of software application development teams that develop, design, program and test software applications.
|
||||||
|
- **System Development Life Cycle (SDLC)**: A process for creating and altering computer applications through an approach that includes planning, system analysis, design, implementation, and system maintenance
|
||||||
|
- **Unified Modeling Language (UML)**: set of graphical notation techniques to create computer models and applications. It could be said that UML is a "blueprint" for developing applications
|
||||||
|
- Application Architects: design different parts of applications
|
||||||
|
- Middleware
|
||||||
|
- Programming Infrastructure
|
||||||
|
|
||||||
|
### 16.4: Information Technology Jobs Contd.
|
||||||
|
|
||||||
|
- Database Administrators (DBAs): the wizards of databases and data requirements
|
||||||
|
- Network Administrators
|
||||||
|
- Senior Web Developers
|
||||||
|
- Business Intelligence Analyst
|
||||||
|
- Information Technology Staff Consultants
|
||||||
|
- IT Auditors
|
||||||
|
|
||||||
|
> All IT jobs require experience, a degree, or both*
|
||||||
|
|
||||||
|
### 16.5: Enterprise Resource Planning Solution
|
||||||
|
|
||||||
|
- Enterprise Resource Planning (ERP): an overall software solution that attempts to get departments on the same page, allowing them to share information and more easily collaborate with each other
|
||||||
|
|
||||||
|
- Advantages
|
||||||
|
|
||||||
|
- Increase production, collab, & efficiency
|
||||||
|
|
||||||
|
- Revenue cycles and order tracking more easily available; enhances decision making
|
||||||
|
- Disadvantages
|
||||||
|
- Must re-engineer own processes to fit ERP solutions
|
||||||
|
- Expensive
|
||||||
|
- Must have process for tracking new entries to prevent inaccurate data from entering the database
|
||||||
|
- Difficult to modify
|
||||||
|
|
||||||
|
### 16.6: Unified Modeling Language
|
||||||
|
|
||||||
|
- Use case scenarios: "Who" can do "what"
|
||||||
|
- Object-Oriented Analysis (OOA): Is focused on what a computer system does
|
||||||
|
- Object Oriented Design (OOD): Focused on how a computer system what it does
|
||||||
|
- Sequence Diagrams: Illustrations that sow how computer processes related and interact with each other and in what order.
|
||||||
|
|
||||||
|
|
||||||
|
### 16.7: System Development Methodologies
|
||||||
|
|
||||||
|
- System Development Life Cycle
|
||||||
|
- Initiation
|
||||||
|
- Concept Development
|
||||||
|
- Planing
|
||||||
|
- Requirements
|
||||||
|
- Design
|
||||||
|
- Development
|
||||||
|
- Testing
|
||||||
|
- Implementation
|
||||||
|
- Rapid Application Development (RAD)
|
||||||
|
- Develope as you go
|
||||||
|
- Software Prototyping
|
||||||
|
- Prototypes AKA vaporware
|
||||||
Loading…
Reference in New Issue
Block a user