LAB 12 Course Summary

曦与 曦与 墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年,写一次发全网 我也要 + 加入社区

 

DEADLINE: 2021/12/20 23:59

Requirements

1. Please recall your first assignment in the summer vacation and your imagination of the software engineering course

(1) Compared with the course objectives and expectations of your first blog, "I hope to enhance the ability and employment competitiveness of computer major through practical exercise". Compared with the current learning and practice, in what aspects have you achieved your expectations and objectives, what are the deficiencies and why?

(2) Summarize the practice and improvement of this course, including the following contents:

  • Count how many lines of code you have completed in this software engineering practice;
  • How much time does each operation of software engineering practice take? (Make a list)
  • Which assignment impressed you most? Why?
  • How many hours have you spent on soft work practice? How many hours per week on average?
  • What new software has been learned and used;
  • What new tools have been learned and used;
  • What new languages, platforms and methods have been learned and mastered;
  • Other improvements (e.g., teamwork).

2. Write your own ‘The Mythical Man-Month’, which means write experience summary and case analysis in project practice (e.g., personal project, team project).

 

3. What do you want to suggest and tell the next practice, or for you at the beginning of school, for you in your freshman year, and for Mr. Zhang at the beginning of school? And expectations for future generations. In particular, do you want to change team players in the next term?

 

4. Please analyze your team. Software engineering practice is a rare serious team cooperation experience in universities. ‘The construction law’ says that there are several stages of team development. Has your team experienced them and finally reached the "creation" stage?

5. How to prove that you have learned software engineering?

(1) Develop software that meets user needs

It must be published publicly, with actual users, a certain number of users and continuous usage (10 - 100 users can be maintained after 3 days); Instead of making software that no users use.

(2) Through a series of tools, processes and teamwork, we can release "good enough" software within the expected time

Have project planning / requirements / design / implementation / release / maintenance and regular progress release; Instead of being fooled by staying up late, patching things up, working alone, delayed delivery, etc.

(3)The software can be maintained and continuously developed through data presentation.

It's not that the source code can't be found, the code has no documentation, the code can't be compiled, and there is no development information of projects such as task / bug

P.S: Please use data to prove the above contents or focus on one of the choices in your blog.

 

6.*(Optional) Read the classic papers on code quality in software engineering, select one or several from the following literature, and make a reading note in combination with your own reality (for example, how about the quality of your own code, is it a big mud ball, and how to measure the quality of your own code)? Select one or more of the following reference papers:

[1] Stamelos I, Angelis L, Oikonomou A, et al. Code quality analysis in open source software development[J]. Information Systems Journal, 2002, 12(1): 43-60.

[2] Boehm B W, Brown J R, Lipow M. Quantitative evaluation of software quality[C]//Proceedings of the 2nd international conference on Software engineering. IEEE Computer Society Press, 1976: 592-605

[3] Samoladas I, Stamelos I, Angelis L, et al. Open source software development should strive for even greater code maintainability[J]. Communications of the ACM, 2004, 47(10): 83-87

7. Give full play to your personality, including graphics, photos and creativity

 

Tips:

  1. TA can’t notice all students. If your blog can impress TA, you can get higher remark.
  2. Please issue your homework in the section of assignment on CSDN.
  3. The Link of each assignment you would accomplish must be submit to Moodle, or you will lose the score of the assignment.
  4. Each assignment submitted to CSDN must be completed in English.
  5. Everyone should write their own summary.
...全文

相关推荐

AWS Certified Solutions Architect Associate英文视频.rar

├ 01 Introduction To The Course,网盘文件 永久连接 │ │ 001 Introduction Overview 2018.mp4 │ └ 002 The Exam Blue Print.mp4 ├ 02 AWS - 10000 Feet Overview │ │ 003 The History Of AWS So Far.mp4 │ │ 004 AWS - 10000 Foot Overview Part 1.mp4 │ │ 005 AWS - 10000 Foot Overview Part 2.mp4 │ │ 006 AWS - 10000 Foot Overview Part 3.mp4 │ │ 007 AWS - 10000 Foot Overview Part 4.mp4 │ │ 008 Dont Freak Out.mp4 │ │ 009 Sign Up To AWS Free Tier.mp4 │ └ quizzes │ └ 001 10000 Foot Quiz.html ├ 03 Identity Access Management IAM │ │ 010 IAM 101.mp4 │ │ 011 IAM - Lab.mp4 │ │ 012 Create A Billing Alarm - Lab.mp4 │ │ 013 IAM Summary.mp4 │ └ quizzes │ └ 002 IAM - Quiz.html ├ 04 AWS Object Storage and CDN - S3 Glacier and CloudFront │ │ 014 S3 - 101.mp4 │ │ 015 Create an S3 Bucket - Lab.mp4 │ │ 016 Version Control - Lab.mp4 │ │ 017 Cross Region Replication.mp4 │ │ 018 Lifecycle Management Glacier - Lab.mp4 │ │ 019 CloudFront CDN Overview.mp4 │ │ 020 Create a CloudFront CDN - Lab.mp4 │ │ 021 S3 - Security Encryption.mp4 │ │ 022 Storage Gateway.mp4 │ │ 023 Snowball.mp4 │ │ 024 Snowball - Lab.mp4 │ │ 025 S3 Transfer Acceleration.mp4 │ │ 026 Create A Static Website Using S3.mp4 │ │ 027 S3 Summary.mp4 │ └ quizzes │ └ 003 S3 Quiz.html ├ 05 EC2 - The Backbone of AWS │ │ 028 EC2 101 - Part 1.mp4 │ │ 029 EC2 101 - Part 2.mp4 │ │ 030 Lets Get Our Hands Dirty Launch An EC2 Instance - Part 1.mp4 │ │ 031 Lets Get Our Hands Dirty Launch An EC2 Instance - Part 2.mp4 │ │ 032 How To Use Putty Windows Users Only.mp4 │ │ 033 Security Groups Basics.mp4 │ │ 034 Upgrading EBS Volume Types - Lab.mp4 │ │ 035 Creating a Windows EC2 Instance RAID Group.mp4 │ │ 036 Create An AMI - Lab.mp4 │ │ 037 AMIs - EBS Root Volumes vs Instance Store.mp4 │ │ 038 Load Balancers Health Checks.mp4 │ │ 039 Cloud Watch EC2.mp4 │ │ 040 The AWS Command Line EC2.mp4 │ │ 041 Using IAM roles with EC2.mp4 │ │ 042 S3 CLI Regions.mp4 │ │ 043 Using Bootstrap .mp4 │ │ 044 EC2...........

优质网络系统领域创作者

EE308-Lab12-Course Summary

EE308-Lab12-Course SummaryFormat DescriptionSelf-analysisThe Mythical Man-MonthTeam AnalysisWhat I want to say Format Description The Link Your Class https://bbs.csdn.net/forums/MUEE308FZ The Link of Requirement of This Assignment https://bbs.csdn.

调参侠鱼尾

R语言期末复习:从向量索引到分组聚合的知识点汇总

R语言作为统计计算与数据分析的基石,其核心在于数据结构与函数式操作。向量、矩阵、数组、数据框和因子构成了数据组织的基本单元,而基于位置的索引、逻辑索引以及apply族函数则实现了高效的批量运算。掌握这些原理能显著减少类型转换与维度不匹配的常见错误,提升数据清洗、统计建模和可视化的工程效率。在数据科学实践中,从工作空间管理到分组聚合、缺失值处理,处处依赖这些基础知识。这份期末复习知识点汇总,正是围绕数据结构、向量索引、apply族与分组聚合等关键概念展开,帮助学习者在短时间内系统梳理R语言的核心操作。

weixin_33859231

AWS机器学习工程师认证:云原生ML工程交付能力实战指南

机器学习工程化(MLOps)是将算法模型转化为稳定、可监控、可扩展生产服务的关键能力。其核心在于数据工程、模型训练部署、持续监控与安全合规的端到端闭环,而非孤立的算法调优。在AWS云环境中,这一过程高度依赖SageMaker、Glue、CloudWatch等原生服务的协同配置与资源约束决策,例如S3分区策略直接影响Athena查询成本,Serverless Inference的冷启动需权衡MemorySize与Provisioned Concurrency。真实场景中,模型漂移检测、KMS密钥轮换兼容性、P

weixin_33788244

通信行业基于MongoDB的安全合规与性能优化:5G时序数据处理、可查询加密及窗口函数应用

内容概要:本文围绕MongoDB在通信行业的深度应用,系统讲解了可查询加密、时间序列集合、窗口函数与性能诊断四大核心技术。通过详实的代码案例,展示了如何利用可查询加密实现敏感数据合规存储与查询,使用时序集合高效处理5G网络KPI等高频写入场景,借助窗口函数进行经营指标的趋势分析,并结合explain()与查询分析器完成性能调优。文章还涵盖分片一致性检查、索引优化等运维实践,全面覆盖通信系统对安全、性能与扩展性的严苛要求。; 适合人群:具备一定数据库基础,从事通信行业研发、架构或运维工作1-3年的技术人员,尤其是参与5G网络监控、客户数据管理或大数据平台建设的相关人员。; 使用场景及目标:① 实现用户手机号、身份证等敏感信息的加密存储与等值查询,满足安全合规要求;② 构建高吞吐、低延迟的5G基站KPI时序数据存储与分析系统;③ 在数据库层直接完成滑动平均、累计求和等经营分析,减少应用层计算负担;④ 诊断慢查询、验证索引有效性,保障系统高性能运行。; 阅读建议:此资源强调理论与实战结合,建议读者在本地或测试环境部署MongoDB 7.0+版本,动手复现文中代码,重点关注schemaMap配置、时序集合参数选择与窗口函数语法细节,并结合explain执行计划理解底层优化机制,从而真正掌握通信级数据架构的设计精髓。

数智顾问
评论
收藏 已收藏
分享
返回顶部