Android开发中MVC架构实践：从理论到现实挑战与优化方案

引言：MVC架构在Android开发中的重要性
在Android应用开发领域，架构选择直接决定了项目的可维护性、扩展性和团队协作效率。MVC（Model-View-Controller）作为最早且最经典的软件架构模式，虽然在现代开发中面临MVP、MVVM等新兴模式的挑战，但其核心思想依然深刻影响着Android开发实践。
MVC架构将应用分为三个核心组件：
Model（模型）
：负责数据处理和业务逻辑
View（视图）
：负责UI展示和用户交互
Controller（控制器）
：负责协调Model和View，处理用户输入
这种职责分离的设计模式，使得代码结构清晰、易于测试和维护。然而，在Android的特定环境下，MVC的实现并非一帆风顺，开发者需要面对Activity/Fragment生命周期管理、内存泄漏、UI线程阻塞等现实挑战。
本文将从理论基础出发，深入探讨MVC在Android中的具体实现方式，分析常见问题，并提供经过实践检验的优化方案。
MVC架构理论基础
1. MVC模式的核心概念
MVC模式的核心在于
关注点分离
（Separation of Concerns）。通过将应用划分为三个相互独立但又协作的组件，实现了：
高内聚
：每个组件专注于单一职责
低耦合
：组件间依赖关系最小化
可测试性
：各组件可独立进行单元测试
2. Android中MVC的自然映射
Android框架本身就带有MVC的基因：
View层
：XML布局文件、View组件
Controller层
：Activity、Fragment
Model层
：数据实体类、数据库、网络请求
这种自然映射使得MVC成为Android开发中最容易上手的架构模式。
Android MVC架构的实践实现
1. 基础实现示例
让我们通过一个用户登录功能来展示MVC的基础实现：
// Model层：用户数据和业务逻辑
data class User(val username: String, val password: String)

class UserModel {
// 模拟网络请求
suspend fun login(username: String, password: String): Result {
return withContext(Dispatchers.IO) {
try {
// 模拟网络延迟
delay(1000)
if (username == “admin” && password == “123456”) {
Result.success(User(username, password))
} else {
Result.failure(Exception(“用户名或密码错误”))
}
} catch (e: Exception) {
Result.failure(e)
}
}
}
}

// View层：UI组件（XML布局）
/*

*/

// Controller层：Activity
class LoginActivity : AppCompatActivity() {
private lateinit var etUsername: EditText
private lateinit var etPassword: EditText
private lateinit var btnLogin: Button
private lateinit var progressBar: ProgressBar
private lateinit var tvResult: TextView

private val userModel = UserModel()
private val scope = CoroutineScope(Dispatchers.Main + SupervisorJob())

override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_login)

initViews()
setupListeners()
}

private fun initViews() {
etUsername = findViewById(R.id.etUsername)
etPassword = findViewById(R.id.etPassword)
btnLogin = findViewById(R.id.btnLogin)
progressBar = findViewById(R.id.progressBar)
tvResult = findViewById(R.id.tvResult)
}

private fun setupListeners() {
btnLogin.setOnClickListener {
val username = etUsername.text.toString().trim()
val password = etPassword.text.toString().trim()

if (validateInput(username, password)) {
performLogin(username, password)
}
}
}

private fun validateInput(username: String, password: String): Boolean {
if (username.isEmpty()) {
tvResult.text = “请输入用户名”
return false
}
if (password.isEmpty()) {
tvResult.text = “请输入密码”
return false
}
if (password.length < 6) { tvResult.text = "密码长度不能少于6位" return false } return true } private fun performLogin(username: String, password: String) { // 更新UI状态 progressBar.visibility = View.VISIBLE btnLogin.isEnabled = false tvResult.text = "" scope.launch { val result = userModel.login(username, password) // 更新UI progressBar.visibility = View.GONE btnLogin.isEnabled = true result.onSuccess { user ->
tvResult.text = “登录成功: ${user.username}”
tvResult.setTextColor(Color.GREEN)
}.onFailure { exception ->
tvResult.text = “登录失败: ${exception.message}”
tvResult.setTextColor(Color.RED)
}
}
}

override fun onDestroy() {
super.onDestroy()
scope.cancel() // 防止协程泄漏
}
}
2. 代码结构分析
上述示例展示了MVC的基础实现：
Model
：
UserModel
负责数据验证和网络请求
View
：XML布局定义UI结构
Controller
：
LoginActivity
处理用户输入、调用Model、更新View
3. 现实挑战：MVC在Android中的常见问题
3.1 Activity/Fragment 职责过重（上帝对象）
问题描述
：
在实际开发中，Activity/Fragment往往承担了过多职责：
处理UI交互
业务逻辑验证
网络请求调用
数据解析
状态管理
生命周期处理
这导致Activity类膨胀，难以维护和测试。
3.2 内存泄漏风险
问题场景
：
// 问题代码：匿名内部类持有外部Activity引用
class ProblematicActivity : AppCompatActivity() {
private val userModel = UserModel()

override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)

// 错误：匿名内部类隐式持有Activity引用
btnLogin.setOnClickListener {
userModel.login(username, password, object : Callback {
override fun onSuccess(user: User) {
// 这里持有Activity引用，如果请求在Activity销毁后完成，会导致内存泄漏
updateUI(user)
}

override fun onError(error: String) {
showError(error)
}
})
}
}
}
3.3 测试困难
问题描述
：
由于Controller（Activity）与Android框架紧密耦合，且同时包含UI逻辑和业务逻辑，导致：
单元测试需要启动Android环境，速度慢
UI测试和业务逻辑测试混杂
难以模拟各种边界条件
3.4 异步任务管理复杂
问题场景
：
// 问题代码：多个异步任务难以协调
class ComplexActivity : AppCompatActivity() {
private var job1: Job? = null
private var job2: Job? = null
private var job3: Job? = null

// 多个并行任务，状态管理混乱
fun loadData() {
job1 = scope.launch { /* … */ }
job2 = scope.launch { /* … */ }
job3 = scope.launch { /* … */ }
}

// 清理时容易遗漏
override fun onDestroy() {
super.onDestroy()
job1?.cancel()
job2?.cancel()
// 漏了job3
}
}
优化方案：从基础MVC到增强型MVC
1. 优化方案一：职责细化与辅助类
1.1 创建UI辅助类
// UI辅助类：专门处理UI更新
class LoginUIHelper(
private val activity: AppCompatActivity,
private val etUsername: EditText,
private val etPassword: EditText,
private val btnLogin: Button,
private val progressBar: ProgressBar,
private val tvResult: TextView
) {
fun showLoading() {
progressBar.visibility = View.VISIBLE
btnLogin.isEnabled = false
etUsername.isEnabled = false
etPassword.isEnabled = false
}

fun hideLoading() {
progressBar.visibility = View.GONE
btnLogin.isEnabled = true
etUsername.isEnabled = true
etPassword.isEnabled = true
}

fun showSuccess(message: String) {
tvResult.text = message
tvResult.setTextColor(Color.GREEN)
}

fun showError(message: String) {
tvResult.text = message
tvResult.setTextColor(Color.RED)
}

fun clearResult() {
tvResult.text = “”
}

fun getUsername(): String = etUsername.text.toString().trim()
fun getPassword(): String = etPassword.text.toString().trim()
}

// 输入验证器
class InputValidator {
fun validateUsername(username: String): ValidationResult {
return when {
username.isEmpty() -> ValidationResult.Error(“请输入用户名”)
username.length < 3 -> ValidationResult.Error(“用户名至少3个字符”)
else -> ValidationResult.Success
}
}

fun validatePassword(password: String): ValidationResult {
return when {
password.isEmpty() -> ValidationResult.Error(“请输入密码”)
password.length < 6 -> ValidationResult.Error(“密码至少6位”)
else -> ValidationResult.Success
}
}
}

sealed class ValidationResult {
object Success : ValidationResult()
data class Error(val message: String) : ValidationResult()
}
1.2 重构后的Controller
class OptimizedLoginActivity : AppCompatActivity() {
private lateinit var uiHelper: LoginUIHelper
private lateinit var validator: InputValidator
private val userModel = UserModel()
private val scope = CoroutineScope(Dispatchers.Main + SupervisorJob())

override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_login)

initDependencies()
setupUI()
setupListeners()
}

private fun initDependencies() {
uiHelper = LoginUIHelper(
activity = this,
etUsername = findViewById(R.id.etUsername),
etPassword = findViewById(R.id.etPassword),
btnLogin = findViewById(R.id.btnLogin),
progressBar = findViewById(R.id.progressBar),
tvResult = findViewById(R.id.tvResult)
)
validator = InputValidator()
}

private fun setupUI() {
// 可以在这里恢复状态
if (savedInstanceState != null) {
// 恢复UI状态
}
}

private fun setupListeners() {
findViewById

(R.id.btnLogin).setOnClickListener {
handleLoginClick()
}
}

private fun handleLoginClick() {
uiHelper.clearResult()

// 验证输入
val username = uiHelper.getUsername()
val password = uiHelper.getPassword()

when (val usernameResult = validator.validateUsername(username)) {
is ValidationResult.Error -> {
uiHelper.showError(usernameResult.message)
return
}
ValidationResult.Success -> { /* 继续 */ }
}

when (val passwordResult = validator.validatePassword(password)) {
is ValidationResult.Error -> {
uiHelper.showError(passwordResult.message)
return
}
ValidationResult.Success -> { /* 继续 */ }
}

// 执行登录
performLogin(username, password)
}

private fun performLogin(username: String, password: String) {
uiHelper.showLoading()

scope.launch {
val result = userModel.login(username, password)

uiHelper.hideLoading()

result.onSuccess { user ->
uiHelper.showSuccess(“登录成功: ${user.username}”)
navigateToMain()
}.onFailure { exception ->
uiHelper.showError(“登录失败: ${exception.message}”)
}
}
}

private fun navigateToMain() {
startActivity(Intent(this, MainActivity::class.java))
finish()
}

override fun onDestroy() {
super.onDestroy()
scope.cancel()
}

// 状态保存与恢复
override fun onSaveInstanceState(outState: Bundle) {
super.onSaveInstanceState(outState)
outState.putString(“username”, uiHelper.getUsername())
}

override fun onRestoreInstanceState(savedInstanceState: Bundle) {
super.onRestoreInstanceState(savedInstanceState)
val username = savedInstanceState.getString(“username”, “”)
// 恢复UI状态
}
}
2. 优化方案二：引入Repository模式
// Repository层：数据源抽象
class UserRepository(
private val apiService: ApiService,
private val localDataSource: LocalDataSource
) {
suspend fun login(username: String, password: String): Result {
return try {
// 先尝试本地验证
val localUser = localDataSource.getUser(username)
if (localUser != null && localUser.password == password) {
return Result.success(localUser)
}

// 本地验证失败，调用网络API
val response = apiService.login(username, password)
if (response.isSuccessful) {
val user = response.body() ?: return Result.failure(Exception(“Empty response”))
// 保存到本地
localDataSource.saveUser(user)
Result.success(user)
} else {
Result.failure(Exception(“Login failed: ${response.code()}”))
}
} catch (e: Exception) {
Result.failure(e)
}
}

suspend fun getUserProfile(userId: String): Result {
return try {
// 优先从缓存获取
localDataSource.getUserProfile(userId)?.let {
return Result.success(it)
}

// 缓存未命中，调用API
val response = apiService.getUserProfile(userId)
if (response.isSuccessful) {
val profile = response.body() ?: return Result.failure(Exception(“Empty response”))
localDataSource.saveUserProfile(profile)
Result.success(profile)
} else {
Result.failure(Exception(“Failed to fetch profile”))
}
} catch (e: Exception) {
Result.failure(e)
}
}
}

// 数据源接口
interface LocalDataSource {
suspend fun getUser(username: String): User?
suspend fun saveUser(user: User)
suspend fun getUserProfile(userId: String): UserProfile?
suspend fun saveUserProfile(profile: UserProfile)
}

// 网络API接口
interface ApiService {
@POST(“login”)
suspend fun login(
@Body request: LoginRequest
): Response

@GET(“user/{userId}/profile”)
suspend fun getUserProfile(
@Path(“userId”) userId: String
): Response
}
3. 优化方案三：状态管理与事件总线
// 统一状态管理
sealed class LoginState {
object Idle : LoginState()
object Loading : LoginState()
data class Success(val user: User) : LoginState()
data class Error(val message: String) : LoginState()
}

// 事件总线（简化版）
class EventBus {
private val listeners = mutableListOf()

fun subscribe(listener: EventListener) {
listeners.add(listener)
}

fun unsubscribe(listener: EventListener) {
listeners.remove(listener)
}

fun publish(event: Any) {
listeners.forEach { it.onEvent(event) }
}

interface EventListener {
fun onEvent(event: Any)
}
}

// 增强的Controller
class AdvancedLoginActivity : AppCompatActivity(), EventBus.EventListener {
private lateinit var uiHelper: LoginUIHelper
private lateinit var validator: InputValidator
private val userModel = UserModel()
private val eventBus = EventBus()
private val scope = CoroutineScope(Dispatchers.Main + SupervisorJob())

private var currentState: LoginState = LoginState.Idle

override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_login)

initDependencies()
setupListeners()
eventBus.subscribe(this)

// 恢复状态
restoreState(savedInstanceState)
}

private fun initDependencies() {
uiHelper = LoginUIHelper(
activity = this,
etUsername = findViewById(R.id.etUsername),
etPassword = findViewById(R.id.etPassword),
btnLogin = findViewById(R.id.btnLogin),
progressBar = findViewById(R.id.progressBar),
tvResult = findViewById(R.id.tvResult)
)
validator = InputValidator()
}

private fun setupListeners() {
findViewById

(R.id.btnLogin).setOnClickListener {
handleLoginClick()
}
}

private fun handleLoginClick() {
val username = uiHelper.getUsername()
val password = uiHelper.getPassword()

// 验证输入
if (!validateInputs(username, password)) return

// 发起登录事件
eventBus.publish(LoginEvent(username, password))
}

private fun validateInputs(username: String, password: String): Boolean {
uiHelper.clearResult()

return when (val result = validator.validateUsername(username)) {
is ValidationResult.Error -> {
uiHelper.showError(result.message)
false
}
ValidationResult.Success -> when (val pwdResult = validator.validatePassword(password)) {
is ValidationResult.Error -> {
uiHelper.showError(pwdResult.message)
false
}
ValidationResult.Success -> true
}
}
}

// 事件处理
override fun onEvent(event: Any) {
when (event) {
is LoginEvent -> performLogin(event.username, event.password)
is NavigationEvent -> handleNavigation(event)
}
}

private fun performLogin(username: String, password: String) {
updateState(LoginState.Loading)

scope.launch {
val result = userModel.login(username, password)

when {
result.isSuccess -> {
val user = result.getOrNull()!!
updateState(LoginState.Success(user))
eventBus.publish(NavigationEvent.Destination.Main)
}
result.isFailure -> {
val error = result.exceptionOrNull()?.message ?: “Unknown error”
updateState(LoginState.Error(error))
}
}
}
}

private fun updateState(state: LoginState) {
currentState = state
when (state) {
is LoginState.Idle -> {
uiHelper.hideLoading()
uiHelper.clearResult()
}
is LoginState.Loading -> {
uiHelper.showLoading()
}
is LoginState.Success -> {
uiHelper.hideLoading()
uiHelper.showSuccess(“登录成功: ${state.user.username}”)
}
is LoginState.Error -> {
uiHelper.hideLoading()
uiHelper.showError(state.message)
}
}
}

private fun handleNavigation(event: NavigationEvent) {
when (event) {
is NavigationEvent.Destination.Main -> {
startActivity(Intent(this, MainActivity::class.java))
finish()
}
is NavigationEvent.Destination.Back -> {
finish()
}
}
}

// 状态保存与恢复
override fun onSaveInstanceState(outState: Bundle) {
super.onSaveInstanceState(outState)
outState.putSerializable(“state”, currentState)
outState.putString(“username”, uiHelper.getUsername())
}

private fun restoreState(savedInstanceState: Bundle?) {
savedInstanceState?.let {
val state = it.getSerializable(“state”) as? LoginState
val username = it.getString(“username”, “”)

// 恢复UI
if (username.isNotEmpty()) {
// 恢复用户名输入
}

// 恢复状态
state?.let { s -> updateState(s) }
}
}

override fun onDestroy() {
super.onDestroy()
eventBus.unsubscribe(this)
scope.cancel()
}
}

// 事件定义
data class LoginEvent(val username: String, val password: String)

sealed class NavigationEvent {
object Destination {
object Main : NavigationEvent()
object Back : NavigationEvent()
}
}
4. 优化方案四：依赖注入与组件化
// 依赖注入容器
object ServiceLocator {
private var apiService: ApiService? = null
private var localDataSource: LocalDataSource? = null
private var userRepository: UserRepository? = null

fun getApiService(): ApiService {
return apiService ?: createApiService().also { apiService = it }
}

fun getLocalDataSource(): LocalDataSource {
return localDataSource ?: RoomDataSource().also { localDataSource = it }
}

fun getUserRepository(): UserRepository {
return userRepository ?: UserRepository(
apiService = getApiService(),
localDataSource = getLocalDataSource()
).also { userRepository = it }
}

private fun createApiService(): ApiService {
// 创建Retrofit实例
return Retrofit.Builder()
.baseUrl(“https://api.example.com/”)
.addConverterFactory(GsonConverterFactory.create())
.build()
.create(ApiService::class.java)
}
}

// 使用依赖注入的Activity
class DIActivity : AppCompatActivity() {
// 通过懒加载获取依赖
private val userRepository by lazy { ServiceLocator.getUserRepository() }
private val validator by lazy { InputValidator() }
private val uiHelper by lazy {
LoginUIHelper(
activity = this,
etUsername = findViewById(R.id.etUsername),
etPassword = findViewById(R.id.etPassword),
btnLogin = findViewById(R.id.btnLogin),
progressBar = findViewById(R.id.progressBar),
tvResult = findViewById(R.id.tvResult)
)
}

private val scope = CoroutineScope(Dispatchers.Main + SupervisorJob())

override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_login)

setupListeners()
}

private fun setupListeners() {
findViewById

(R.id.btnLogin).setOnClickListener {
handleLogin()
}
}

private fun handleLogin() {
val username = uiHelper.getUsername()
val password = uiHelper.getPassword()

if (!validateInputs(username, password)) return

uiHelper.showLoading()

scope.launch {
val result = userRepository.login(username, password)

uiHelper.hideLoading()

result.onSuccess { user ->
uiHelper.showSuccess(“登录成功: ${user.username}”)
navigateToMain()
}.onFailure { exception ->
uiHelper.showError(“登录失败: ${exception.message}”)
}
}
}

private fun validateInputs(username: String, password: String): Boolean {
uiHelper.clearResult()

return when (val result = validator.validateUsername(username)) {
is ValidationResult.Error -> {
uiHelper.showError(result.message)
false
}
ValidationResult.Success -> when (val pwdResult = validator.validatePassword(password)) {
is ValidationResult.Error -> {
uiHelper.showError(pwdResult.message)
false
}
ValidationResult.Success -> true
}
}
}

private fun navigateToMain() {
startActivity(Intent(this, MainActivity::class.java))
finish()
}

override fun onDestroy() {
super.onDestroy()
scope.cancel()
}
}
性能优化与最佳实践
1. 内存泄漏防护
// 使用ViewModel + LiveData（虽然这是MVVM的组件，但在MVC中也可借鉴）
class LoginViewModel : ViewModel() {
private val _loginState = MutableLiveData()
val loginState: LiveData = _loginState

private val scope = CoroutineScope(Dispatchers.Main + SupervisorJob())

fun login(username: String, password: String) {
_loginState.value = LoginState.Loading

scope.launch {
// 模拟登录
delay(2000)
_loginState.value = LoginState.Success(User(username, password))
}
}

override fun onCleared() {
super.onCleared()
scope.cancel()
}
}

// 在Activity中观察
class LoginActivity : AppCompatActivity() {
private val viewModel by viewModels()
private lateinit var uiHelper: LoginUIHelper

override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_login)

initDependencies()
setupObservers()
setupListeners()
}

private fun setupObservers() {
viewModel.loginState.observe(this) { state ->
when (state) {
is LoginState.Loading -> uiHelper.showLoading()
is LoginState.Success -> {
uiHelper.hideLoading()
uiHelper.showSuccess(“登录成功: ${state.user.username}”)
}
is LoginState.Error -> {
uiHelper.hideLoading()
uiHelper.showError(state.message)
}
else -> {}
}
}
}

private fun setupListeners() {
findViewById

(R.id.btnLogin).setOnClickListener {
val username = uiHelper.getUsername()
val password = uiHelper.getPassword()

if (validateInputs(username, password)) {
viewModel.login(username, password)
}
}
}

private fun validateInputs(username: String, password: String): Boolean {
// 验证逻辑…
return true
}
}
2. 网络请求优化
// 封装网络请求，统一处理错误
class SafeApiCall {
suspend fun safeApiCall(
apiCall: suspend () -> Response
): Result = withContext(Dispatchers.IO) {
try {
val response = apiCall()
if (response.isSuccessful) {
response.body()?.let {
Result.success(it)
} ?: Result.failure(Exception(“Response body is null”))
} else {
val errorBody = response.errorBody()?.string() ?: “Unknown error”
Result.failure(Exception(“API Error: ${response.code()} – $errorBody”))
}
} catch (e: Exception) {
Result.failure(e)
}
}
}

// 在Repository中使用
class UserRepository(
private val apiService: ApiService,
private val localDataSource: LocalDataSource,
private val safeApiCall: SafeApiCall
) {
suspend fun login(username: String, password: String): Result {
return safeApiCall.safeApiCall {
apiService.login(LoginRequest(username, password))
}.map { user ->
// 保存到本地
localDataSource.saveUser(user)
user
}
}
}
3. 测试策略
// 单元测试示例
class UserModelTest {
private lateinit var userModel: UserModel

@Before
fun setup() {
userModel = UserModel()
}

@Test
fun `login with valid credentials returns success`() = runTest {
val result = userModel.login(“admin”, “123456”)
assertTrue(result.isSuccess)
assertEquals(“admin”, result.getOrNull()?.username)
}

@Test
fun `login with invalid credentials returns failure`() = runTest {
val result = userModel.login(“wrong”, “wrong”)
assertTrue(result.isFailure)
}
}

// UI测试示例
class LoginActivityTest {
@get:Rule
val activityRule = ActivityScenarioRule(LoginActivity::class.java)

@Test
fun testLoginFlow() {
onView(withId(R.id.etUsername)).perform(typeText(“admin”))
onView(withId(R.id.etPassword)).perform(typeText(“123456”))
onView(withId(R.id.btnLogin)).perform(click())

onView(withId(R.id.progressBar)).check(matches(isDisplayed()))
onView(withText(“登录成功: admin”)).check(matches(isDisplayed()))
}
}
总结与建议
1. MVC在Android中的适用场景
MVC架构最适合以下场景：
小型项目
：代码量不大，结构简单
快速原型开发
：需要快速验证想法
学习和教学
：理解架构概念的基础
简单CRUD应用
：数据展示和操作为主
2. 何时考虑升级架构
当项目出现以下情况时，应考虑迁移到MVP或MVVM：
Activity类超过500行
：职责过重
难以进行单元测试
：业务逻辑与UI耦合严重
团队协作困难
：多人开发时冲突频繁
需要复杂的状态管理
：UI状态多样且变化频繁
3. 优化MVC的核心原则
单一职责
：每个类只做一件事
依赖倒置
：高层模块不依赖低层模块
控制反转
：通过依赖注入管理对象创建
状态管理
：集中管理UI状态
异步封装
：统一处理协程和线程切换
4. 最终建议
虽然MVC是Android开发的起点，但通过合理的优化和增强，它仍然可以应对中等复杂度的应用开发。关键在于：
不要教条化
：根据项目实际需求选择合适的架构
持续重构
：随着项目演进不断优化代码结构
团队共识
：确保团队成员对架构理解一致
工具辅助
：使用Lint、Detekt等工具保持代码质量
记住，
没有最好的架构，只有最适合的架构
。MVC作为基础，其核心思想——关注点分离，是所有现代架构模式的共同基础。掌握好MVC，将为学习其他架构模式打下坚实的基础。